Conversation
Summary of ChangesHello @AlpinDale, 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 addresses an issue where the 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.
Code Review
This pull request introduces several improvements to model configuration handling. It adds support for max_target_positions to correctly determine the maximum length for Whisper models. Additionally, it enhances the RoPE scaling logic by making it more robust to legacy configuration keys and by correctly excluding gemma3 models, which do not require this scaling. The changes are well-reasoned and improve the codebase's reliability. I have one minor suggestion to make the model type check case-insensitive for better robustness.
| # NOTE: Gemma3's max_model_len is already scaled by RoPE scaling | ||
| if rope_scaling is not None and "gemma3" not in getattr( | ||
| hf_config, "model_type", "" | ||
| ): |
There was a problem hiding this comment.
The check for the gemma3 model type is case-sensitive. To make it more robust, it's advisable to convert the model type to lowercase before the comparison. This will ensure the check works correctly even if the model type is specified with different casing, such as 'Gemma3'.
| ): | |
| ).lower(): |
No description provided.