Repository navigation
0.1.4: stop truncating stdout at 64 KiB through a pipe - #5
Merged
Merged
Conversation
process.exit() dropped output still queued on the pipe. Set process.exitCode and let the loop drain. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
coderbuzz
force-pushed
the
fix-stdout-truncation
branch
from
October 12, 2026 14:04
62e0a38 to
42bd4cd
Compare
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
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.
Summary
process.exit(code)insrc/cli.tsdropped stdout still queued on a pipe, so--json/--stream-jsonoutput over 64 KiB was cut at 65,536 bytes (exit 0, invalid JSON). Now setsprocess.exitCodeand lets the loop drain.npm test9/9. Verified against the real API: 242 KB via pipe, valid JSON.🤖 Generated with Claude Code