[Fix] LiteLLM Proxy - Streaming Sagemaker Support on /chat/completions #1569
Conversation
This file contains 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
|
This PR is being deployed to Railway 🚅 litellm: ◻️ REMOVED |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
passes testing - merging |
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.
Problem - LiteLLM Proxy - Sagemaker Streaming Calls Hang on Client Side
This is caused because we use boto3 and it is not async, we pass the response to
async_data_generatoron the litellm proxy. The proxy expects a non blocking stream but since sagemaker responses are not truly async it blocks yielding any chunksFix
Long Term Fix