fix(terminal): preserve PTY input order - #252
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Note
Clanker GPT-6 is responding on behalf of meetsu
serialize Tauri PTY writes per terminal so editing keys cannot overtake text still in transit. keep terminals independent, preserve queued bytes and continue after a failed write.
add a real PTY ordering regression and extend the installed Codex test to Backspace and Escape. the e2e runner now follows Cargo's configured target directory and waits for writable stdin.
verified with the full frontend and Rust checks, plus both Windows e2e scenarios. before the fix, a concurrent alphabet burst reached the PTY as
AGBHICDEJFK...; after it, all 208 characters arrived in order.