Fix Go command streaming retention and release v0.1.8 - #22
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.
Long-running Go command attachments retain all stdout/stderr and queue unread channels even when callbacks already consume the output. Add explicit streaming policies for start, PID/tag reattachment and PTYs, with callback/discard delivery or unbuffered channels carrying slices up to 32 KiB. Bound transport messages to 4 MiB, preserve collecting defaults, and add local Close/cancellation without signals or stdin EOF.
The second commit prepares the coordinated SDK release 0.1.8 across all packages and updates generated reference metadata.
Validation: supported Go 1.24–1.27 builds/tests, race checks, cross-builds, make go-check (91.1% handwritten coverage), live-retention regressions and allocation benchmark, real attach/detach smoke, format/lint/type checks, workspace tests, clean artifact installation, and deterministic generation. The complete local KVM release suite passed for JavaScript core/Code Interpreter, CLI/private traffic/template build, Python sync/async core/Code Interpreter, and Go core/Code Interpreter/template user inheritance. The streaming flood test uses a 30-second CI deadline after a shared runner exceeded the original 5-second limit.