Skip to content

Conversation

@ZZHbible
Copy link
Contributor

@ZZHbible ZZHbible commented Jan 9, 2026

This PR fixes the FP8 + quantization check by using model_args.quantization_bit instead of training_args.quantization_bit, since quantization bits belong to model loading config and may not be present in training_args.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @ZZHbible, 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 resolves an issue where the compatibility check between FP8 training and model quantization was using an incorrect parameter source. By switching the reference from training_args to model_args for the quantization_bit, the system now accurately validates these configurations, preventing potential misconfigurations or runtime errors related to mixed precision training.

Highlights

  • FP8 and Quantization Check Fix: The pull request corrects the logic for checking compatibility between FP8 training and quantization. Previously, the check incorrectly referenced training_args.quantization_bit, which might not always be present or accurate for model-specific quantization settings. This change updates the check to use model_args.quantization_bit, ensuring that the validation correctly identifies when FP8 training is incompatible with a model's quantization configuration.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 correctly fixes a bug where the check for conflicting FP8 and quantization settings was using training_args.quantization_bit instead of model_args.quantization_bit. Since quantization settings are part of the model configuration, this change correctly aligns the validation logic with the argument structure. The fix is accurate and improves the code's correctness.

Copy link
Owner

@hiyouga hiyouga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice catch

@hiyouga hiyouga merged commit 5aacbe8 into hiyouga:main Jan 9, 2026
17 checks passed
@hiyouga hiyouga added the solved This problem has been already solved label Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

solved This problem has been already solved

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants