-
Notifications
You must be signed in to change notification settings - Fork 349
feat(sandbox): detached PTY exec — run long commands without holding a connection #2558
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
3 commits
Select commit
Hold shift + click to select a range
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
Oops, something went wrong.
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.
RISK — stale
_replay_gapcan spuriously fail a reused session's detached run._replay_gapis a monotonic per-session accumulator (pty.py:151) that is never reset.run_detachedchecksif self._replay_gap:(pty.py:370) to detect output evicted during this command, but the counter also gets bumped by the ordinary connection-loss recovery path:_reattach_socketre-dials withsince=self._received, and if the server evicted bytes during the outage,_pump_socketincrements_replay_gap.What breaks: an explicitly-passed live session that survived one socket drop with eviction (exactly the case
_pump/_reattach_socketexist to handle in the proxy-shedding environment) carries a nonzero_replay_gapinto a laterpty.exec(..., detach=True). The very first poll's drain then raises "PTY output exceeded the server's retained window" even though this command lost nothing.Blast radius: a false-negative hard failure of an otherwise-successful detached command on a reused session — a spuriously failed eval/training step, not silent corruption (it raises).
Fix: reset the window at the start of
run_detachedso it only measures loss for the current command, e.g. setself._replay_gap = 0right after writing the launch line (before the poll loop atpty.py:357).