Repository navigation
fix: handle remaining response and stream boundary failures - #14
Merged
Merged
Conversation
Reject failed or incomplete non-stream Responses while retaining partial text and usage. Recognize explicit Chat stream errors before [DONE]. Keep stream HTTP error body reads under timeout and cancellation protection. Add 14 regression cases; npm run verify passes with 205 tests.
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.
Fix three boundary cases that could report failed requests as successful or leave error responses waiting past their deadline.
Validation: npm run verify passes (typecheck, lint, 220 tests, production build). Added 29 regression cases, including status checks with text only, usage only, and both; malformed statuses; and explicit errors overriding completed.
Scope is limited to these three boundary fixes and their regression tests.