fix: accept Azure assistant file ids#5759
Open
he-yufeng wants to merge 2 commits into
Open
Conversation
6c74218 to
90a0e69
Compare
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.
Fixes #5664.
Summary
This updates the LiteLLM file-id path to treat Azure
assistant-*ids the same way it already treatsfile-*ids for OpenAI/Azure providers.Without this, an Azure-uploaded assistant file id can fall through the file URI fallback path instead of being sent as a Responses API file content block.
Verification
Ran locally on Windows:
Result:
Note:
uv run --extra test ...is currently blocked for me on Windows because the lockedyarl==1.24.1resolution has no Windows wheel. I installed the minimal target-test dependencies in the local venv and ran the focused test path above.