fix(osc): guard params[1] access in OSC 1337 arm against missing second param

[adhavan18]

Description

adds a params.len() < 2 guard at the top of the b"1337" arm in osc_dispatch so a parameterless OSC 1337 sequence is treated as unhandled instead of panicking.

Linked Issue

• The linked issue is labeled ready-to-spec or ready-to-implement.

fixes #12817

Root cause

app/src/terminal/model/ansi/mod.rs, osc_dispatch, the b"1337" arm directly accesses params[1] without a length guard. every neighboring OSC arm (133, 777, 52, 9277, 9278) checks params.len() before accessing any param beyond index 0 — the 1337 arm was the only exception.

when the sequence has no second parameter (params == [b"1337"]), params[1] is out of bounds → panic.

Fix

three lines added at the top of the b"1337" arm:

if params.len() < 2 {
    return unhandled(params);
}

this is identical to the guard pattern already used by b"133", b"777", b"52", and others.

Testing

• I have manually tested my changes locally with ./script/run

added a regression unit test in mod_tests.rs:

#[test]
fn parse_osc1337_without_second_param_does_not_panic() {
    let bytes: &[u8] = b"\x1b]1337\x07";
    let _ = parse_bytes(bytes); // must not panic
}

manual test: printf '\e]1337\a' in a running warp session no longer crashes.

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

CHANGELOG-BUG-FIX: fix panic when receiving a bare OSC 1337 sequence without a second parameter

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @adhavan18 on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

[oz-for-oss]

@adhavan18

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #12817, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

[oz-for-oss]

@adhavan18

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #12817, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz