feat: streaming response for tts - #1122
Merged
Merged
Conversation
x22x22
pushed a commit
to x22x22/new-api
that referenced
this pull request
Apr 24, 2026
feat: streaming response for tts
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
2 participants
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.
The status code has been judged before, if there is a body reading failure, it should be regarded as a non-recoverable error, so it should not return err for external retry. Analogous to nginx's load balancing, it will only retry if it can't be requested or if the upstream returns a specific status code, once the upstream has already written the header, the subsequent failure of the response body should be regarded as a non-recoverable error, and can be terminated directly.