Repository navigation
chore(cost-map): take azure max input for deepseek-v3.2, grok-4 and grok-code-fast-1 #43609
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
berriai-litellm-provider-info-sync
wants to merge
1
commit into
main
from
litellm-providers/price-sync-azure
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
litellm.modify_paramsis enabled, this change makes DeepSeek-V3.2’s input limit equal its unchanged 128,000-token output limit. For a completion that requests a large output, LiteLLM now treats those limits as one shared budget and subtracts the prompt tokens frommax_tokens, silently shortening the requested output. The Azure listing presents input and output as separate limits; please verify that the endpoint requires a combined budget before this input-only update changes output lengths. The backup map has the same change.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Azure states 128,000 input and 128,000 output for DeepSeek-V3.2; deepseek-v3.2-speciale and deepseek/deepseek-v3.2 already carry equal limits, so the shared-budget clamp matches siblings
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. Azure documents these as separate limits—128,000 input and 128,000 output—and the existing
deepseek-v3.2-speciale/deepseek/deepseek-v3.2catalog entries establish the same equal-limit representation. I don't have evidence thatmodify_paramstreatsmax_input_tokensandmax_output_tokensas a shared output budget; my earlier claim about subtracting prompt tokens frommax_tokenswas incorrect. This input-limit update is therefore consistent with the provider documentation and sibling entries; no change is needed.