fix: incorrect default max_tokens set - legacy issue #4451
Merged
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.
Describe Your Changes
Fixes Issues
max_tokens
automatically revert back to 8192 when users create a new thread #4372Self Checklist
This pull request includes a small but important change to the
ModelDropdown
component in theweb/containers/ModelDropdown/index.tsx
file. The change involves updating the property name used to determine the maximum number of tokens allowed.web/containers/ModelDropdown/index.tsx
: Changedmodel?.parameters.token_limit
tomodel?.parameters.max_tokens
to correctly reference the maximum tokens parameter.