fix:Local DB conflicts with model and defaultSetting #124
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
message:If the model saved in the local DB does not exist in the default setting, it will be automatically updated to the first model in the model list options in the default setting.
❌ Deploy Preview for chatgpt-demo-v2 failed.
|
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
If the model saved in the local DB does not exist in the default setting, it will be automatically updated to the first model in the model list options in the default setting.
Linked Issues
Additional context
For example, if I originally provided GPT4 services, but later only want to provide GPT3.5, the default database settings will cause the optional model list in the updated settings to be invalid. As long as the user does not manually adjust the selected model, the GPT4 model will always be used.