Repository navigation
Retry interrupted streamed polling responses - #124
Open
agocharbhatia wants to merge 1 commit into
Open
agocharbhatia wants to merge 1 commit into
agocharbhatia wants to merge 1 commit into
Conversation
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
With
stream_response_to, a connection that drops while reading the result body raises a rawClientPayloadErrorand skips the existing polling retries. Catch it at the response-read boundary so the SDK retries the GET without submitting the conversion again.Evidence
After: one POST and two GETs produce the complete output.
This covers
aiohttp.ClientErrorduring body reads. It does not change timeout handling.Merge Danger
Door: Two-way.
Blast Radius: Streamed polling.
Known error statuses retain their existing retry classification. Submission retries and public APIs are unchanged.