fix(provider): apply chunkTimeout to non-SSE streaming protocols#35743
Open
trollkarlen wants to merge 1 commit into
Open
fix(provider): apply chunkTimeout to non-SSE streaming protocols#35743trollkarlen wants to merge 1 commit into
trollkarlen wants to merge 1 commit into
Conversation
wrapSSE only installed chunk-timeout monitoring when the response content-type included text/event-stream, so AWS Bedrock (application/vnd.amazon.eventstream) and other EventStream providers bypassed it entirely and chunkTimeout never fired. Match text/event-stream and eventstream content types, and add an optional per-provider chunkTimeoutContentTypes list to include extra content-type substrings in the check. Closes anomalyco#26487
Author
|
Please review so I can rebase and update. |
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.
wrapSSE only installed chunk-timeout monitoring when the response content-type included text/event-stream, so AWS Bedrock (application/vnd.amazon.eventstream) and other EventStream providers bypassed it entirely and chunkTimeout never fired.
Match text/event-stream and eventstream content types, and add an optional per-provider chunkTimeoutContentTypes list to include extra content-type substrings in the check.
Closes #26487
Issue for this PR
Closes #26487
Type of change
What does this PR do?
Add the missing content type and add config for future missing content types.
How did you verify your code works?
Test, and towards the provider.
Screenshots / recordings
Checklist