-
Notifications
You must be signed in to change notification settings - Fork 9.7k
feat(core): enhance availability routing with wrapped fallback and single-model policies #13874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @adamfweidman, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refines the model availability routing by introducing more sophisticated fallback logic. It allows for 'upgrade' fallbacks where a failed model can fall back to a more capable model if available, and ensures that custom models, when explicitly chosen, do not inadvertently trigger fallbacks to other models. This improves the predictability and flexibility of model selection within the core system. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request enhances the model availability routing by introducing two key features: wrapped fallback policies to allow for model upgrades (e.g., Flash to Pro) and strict single-model policies for user-specified custom models to prevent unintended fallbacks. The implementation appears solid and well-tested. The logic for creating fallback candidate lists now correctly wraps around the policy chain. The handling of custom models is now stricter, creating a single-model chain which is the intended behavior. The fallback handler logic has also been refactored for better robustness, especially in scenarios where no suitable fallback model can be found. The accompanying test updates are thorough and cover the new functionality and edge cases well. Overall, this is a high-quality contribution that improves the flexibility and predictability of the model fallback system.
|
Size Change: -103 B (0%) Total Size: 21.4 MB ℹ️ View Unchanged
|
Summary
Enhances the policy-driven fallback mechanism to support "upgrade" fallbacks (e.g., Flash → Pro) via wrapped candidate lists and implements strict single-model policies for user-specified custom models to prevent unwanted fallbacks.
Details
Enhances the policy-driven fallback mechanism to support "upgrade" fallbacks (e.g., Flash → Pro) via wrapped candidate lists and implements strict single-model policies for user-specified custom models to prevent unwanted fallbacks.
Related Issues
Fixes https://github.com/google-gemini/maintainers-gemini-cli/issues/1068
How to Validate
npm run preflight
Pre-Merge Checklist