Skip to content

Conversation

njhill
Copy link
Member

@njhill njhill commented Jun 13, 2025

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.

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]>
@njhill njhill added the bug Something isn't working label Jun 13, 2025
Copy link

👋 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 fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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 ready label to the PR or enable auto-merge.

🚀

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.

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

  1. 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.

@mergify mergify bot added the v1 label Jun 13, 2025
Comment on lines +187 to +190
if wave < self.current_wave:
# If the wave number is stale, ensure the message
# is handled by all the engines.
engine_to_exclude = None
Copy link
Member Author

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.

Comment on lines +221 to +224
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
Copy link
Member Author

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

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 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.

@tlrmchlsmth tlrmchlsmth added the ready ONLY add when PR is ready to merge/full CI is needed label Jun 13, 2025
@tlrmchlsmth tlrmchlsmth enabled auto-merge (squash) June 13, 2025 21:44
@tlrmchlsmth
Copy link
Member

Thanks for fixing this

@tlrmchlsmth tlrmchlsmth merged commit bd517eb into vllm-project:main Jun 14, 2025
76 checks passed
@njhill njhill deleted the fix-dp-wave-msg branch June 14, 2025 01:10
yangw-dev pushed a commit to yangw-dev/vllm that referenced this pull request Jun 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working ready ONLY add when PR is ready to merge/full CI is needed v1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants