-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
[BugFix] Fix DP Coordinator incorrect debug log message #19624
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
Conversation
We were logging "Moving DP wave from N to N" instead of "Moving DP wave from N to (N + 1)" Also included some minor adjacent code improvements. Signed-off-by: Nick Hill <[email protected]>
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add 🚀 |
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.
Summary of Changes
Hello @njhill, 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 primarily addresses a minor bug in the DP Coordinator's debug logging, ensuring that the log message accurately reflects the wave number increment. It also includes a couple of small code improvements for readability and structure.
Highlights
- Bug Fix: Corrected a debug log message in the DP Coordinator that incorrectly reported the wave number transition.
- Code Improvement: Refactored a conditional block and introduced a local variable for clarity in the
process_input_socket
method.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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 is currently in preview and 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 to provide feedback.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
if wave < self.current_wave: | ||
# If the wave number is stale, ensure the message | ||
# is handled by all the engines. | ||
engine_to_exclude = None |
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 is unrelated simplification, this check only applies to the case inside the if
.
new_wave = wave + 1 | ||
logger.debug("Moving DP wave from %d to %d.", | ||
self.current_wave, wave) | ||
self.current_wave = wave + 1 | ||
self.current_wave, new_wave) | ||
self.current_wave = new_wave |
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 is the actual bug fix
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 fixes an incorrect debug log message in the DP Coordinator, ensuring the wave transition is logged accurately. The included adjacent code improvements enhance clarity and precision.
Thanks for fixing this |
…#19624) Signed-off-by: Nick Hill <[email protected]> Signed-off-by: Yang Wang <[email protected]>
We were logging
"Moving DP wave from N to N"
instead of"Moving DP wave from N to (N + 1)"
.Also included some minor adjacent code improvements.
Thanks to @SageMoore for discovering this.