Repository navigation
Cap DeepSeek V4 Flash max output at 262,144 on Posit AI Pass - #125
Merged
Merged
Conversation
Baseten Model APIs rejects max_tokens above 262,144 for deepseek-ai/DeepSeek-V4-Flash-0731, so the 384K limit copied from DeepSeek's native API caused HTTP 400 errors.
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
1 participant
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.
Using DeepSeek V4 Flash through Posit AI Pass fails with:
The Model APIs capability entry for
deepseek-ai/DeepSeek-V4-Flash-0731usedmaxOutputTokens: 384_000, which is DeepSeek's native API limit. Baseten Model APIs caps this model at 262,144, so this lowers the entry to262_144and adds a comment explaining the discrepancy.The direct DeepSeek provider entries in
deepseek-helpers.tsare unchanged, since they target DeepSeek's own API where 384K is the documented limit.ai-config model-capabilities tests pass.