-
Notifications
You must be signed in to change notification settings - Fork 293
fix metrics #1170
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
fix metrics #1170
Conversation
Summary of ChangesHello @WANDY666, 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 a specific edge case in the metrics initialization logic. It ensures that the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. 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 addresses a potential crash in metrics initialization. When args.mtp_step is 0, the code would previously generate an empty list for histogram buckets, leading to a ValueError. The added check correctly handles this edge case by providing a default bucket list. I have one suggestion to improve the code structure for better efficiency and clarity, although the current fix is functionally correct.
| if args.mtp_step == 0: | ||
| mtp_avg_token_per_step_buckets = [1.0, 2.0] |
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.
This correctly handles the case where args.mtp_step is 0. However, the current implementation first computes a list on line 98 (which will be empty if args.mtp_step is 0) and then immediately overwrites it. For better efficiency and readability, it would be preferable to use an if/else block to avoid the unnecessary computation.
You could refactor lines 98-100 like this:
if args.mtp_step == 0:
mtp_avg_token_per_step_buckets = [1.0, 2.0]
else:
mtp_avg_token_per_step_buckets = [i / 10.0 + 1.0 for i in range(0, 10 * args.mtp_step)]This makes the logic more direct and avoids the redundant operation.
No description provided.