feat: set the length of the historical message #75
Conversation
This file contains 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
✅ Deploy Preview for chatgpt-demo-v2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
yzh990918
approved these changes
Jun 26, 2023
yzh990918
requested changes
Jun 26, 2023
Update handler.ts
|
Apologies, I have revised the computation rules for MaxTokens, ensuring that it will no longer yield negative values. |
yzh990918
approved these changes
Jun 28, 2023
|
Thanks! |
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.
Description
Added a button for setting the length of historical messages, and correctly calculates the length of the current user's historical messages upon submission to avoid triggering the MaxTokens error.
This enhancement greatly improves usability.
Linked Issues
Additional context