Add max_tokens configuration for LLM API #421
Merged
Conversation
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
- Implemented loading of chat configuration from a YAML file. - Introduced `get_maxtokens_by_model` function to retrieve max_tokens. - Updated chat completion functions to utilize dynamic max_tokens setting.
kagami-l
approved these changes
Nov 12, 2024
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.
This pull request introduces a new feature for the LLM API by adding a configurable
max_tokenssetting. Changes include:get_maxtokens_by_modelfunction to retrievemax_tokensbased on model selection.max_tokenssetting.This enhancement aims to provide more flexibility in managing the token limits for different models, improving the overall functionality of the API.
Closes /#issue_id