Repository navigation
fix(upstream): retry a stream:false body cut after the 200 header - #2
Merged
Merged
Conversation
A buffered answer whose body broke off ("unexpected EOF") after upstream sent
200 reached the client as HTTP 200 with {"error":...}, so clients never
retried it. Nothing is committed downstream yet, so the loop now treats it like
a far-end 502: a proof row ("body cut: ..."), another lane, bounded by two
passes over the lanes. Raw never returns an error with a 2xx status.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_0114ctFPvApF82aPYWBsVHf2
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.
No description provided.