Fix JSON-RPC pipe reads >64KB by handling short reads #31
+292
−2
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.
Python's
read(n)on pipes doesn't guaranteenbytes—when data exceeds the pipe buffer (~64KB), the kernel returns only what's buffered. This caused JSON parsing failures on large responses.Changes
_read_exact()method: Loops until all requested bytes are read, accumulating chunks from potentially partialread()calls_read_message(): Replaces directread(content_length)with_read_exact(content_length)Reproduction
The fix handles the POSIX behavior where pipe
read()may return fewer bytes than requested, particularly when crossing buffer boundaries.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.