Fix otter: handle preferred_model_default to expensive/cheap migration#289
Open
flexus-teams-stage[bot] wants to merge 1 commit intomainfrom
Open
Fix otter: handle preferred_model_default to expensive/cheap migration#289flexus-teams-stage[bot] wants to merge 1 commit intomainfrom
flexus-teams-stage[bot] wants to merge 1 commit intomainfrom
Conversation
…n in no_special_code_bot and schema
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
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.
no_special_code_bot.py was updated to use two-tier model fields (preferred_model_expensive / preferred_model_cheap), but otters manifest.json and manifest_schema.json still use the legacy preferred_model_default field. This caused a KeyError crash at install time.
Changes:
Otters manifest.json is left unchanged and now works correctly.