Repository navigation
Conversation
In these failures the caller had already closed the connection: the gateway keeps reading Novita's stream, its request context gets cancelled, the read fails, and that read error is logged as a provider fault with a 502. I reproduced it exactly - a deliberately aborted request through the same endpoint produced an identical line (mid-stream read error, provider fault, 502), while the same abort before the first token was correctly recorded as client_canceled/499. Novita was healthy throughout: the same caller finished a 169-second stream on the same model and provider two minutes later, and th… Prepared in the Nexus Control Room; approved by Marc. Co-Authored-By: Nexus Control Room agent <noreply@anthropic.com>
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.
Why
In these failures the caller had already closed the connection: the gateway keeps reading Novita's stream, its request context gets cancelled, the read fails, and that read error is logged as a provider fault with a 502. I reproduced it exactly - a deliberately aborted request through the same endpoint produced an identical line (mid-stream read error, provider fault, 502), while the same abort before the first token was correctly recorded as client_canceled/499. Novita was healthy throughout: the same caller finished a 169-second stream on the same model and provider two minutes later…