-
Notifications
You must be signed in to change notification settings - Fork 933
fix(desktop): v1 terminal — emit legacy marker + gate reattach on streamReady #3389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b578346
Revert "fix(desktop): accept legacy OSC 777 marker in v1 terminal (#3…
Kitenite e95208b
fix(desktop): emit legacy OSC 777 marker alongside 133;A in shell wra…
Kitenite 384ec72
fix(desktop): v1 terminal reattach gate must check streamReady, not c…
Kitenite 2d28085
test(desktop): session resolves readiness on combined 777+133;A wrapp…
Kitenite c15eb8e
Lint
Kitenite File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The three removed tests covered the old daemon-side scanner; the replacement wrapper-level tests (in
shell-wrappers.test.ts) verify that both markers are emitted, but there is no session-level test that verifies the new combined path end-to-end.Concretely, when the session receives
\x1b]777;superset-shell-ready\x07\x1b]133;A\x07:scanForShellReadystrips\x1b]133;A\x07and setsshellReadyState = "ready".\x1b]777;superset-shell-ready\x07is not stripped — it is enqueued viaenqueueEmulatorWriteand broadcast to clients. The PR's "silently dropped by the emulator" claim is correct for xterm.js, but nothing in the test suite currently verifies this pass-through is benign.Consider adding a test analogous to the removed
"strips legacy marker from emitted output"case, but for the new combined sequence:This also catches any future regression where the order of the two markers is accidentally swapped (777 would no longer be in
outputbefore 133;A is consumed).