Skip to content

Conversation

@andyxning
Copy link
Contributor

@andyxning andyxning commented Jul 31, 2025

Essential Elements of an Effective PR Description Checklist

  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.

Purpose

According to the tensor.distributed.send doc, send is a synchronous op.

Test Plan

NA

Test Result

NA

(Optional) Documentation Update

Signed-off-by: Andy Xie <andy.xning@gmail.com>
@github-actions
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.

Code Review

This pull request correctly updates the docstrings for the send methods to indicate that they are blocking operations. My review focuses on improving the docstring format for better clarity and adherence to Python conventions. I've suggested combining the separate string literals into a single, multi-line docstring in all three affected files. This ensures that documentation generation tools will correctly parse the entire comment.

Comment on lines +222 to 223
"""Sends a tensor to the destination rank in a blocking way"""
"""NOTE: `dst` is the local rank of the destination rank."""
Copy link
Contributor

Choose a reason for hiding this comment

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

high

While the change to 'blocking' is correct, the docstring format is unconventional and can be misleading. According to PEP 257, only the first string literal following a function definition is treated as its docstring. Subsequent string literals are simply statements that are evaluated and then discarded, having no effect.

To ensure the entire comment is recognized as the docstring by documentation tools and help(), it should be a single multi-line string.

Suggested change
"""Sends a tensor to the destination rank in a blocking way"""
"""NOTE: `dst` is the local rank of the destination rank."""
"""Sends a tensor to the destination rank in a blocking way.
NOTE: `dst` is the local rank of the destination rank.
"""

Comment on lines +182 to 183
"""Sends a tensor to the destination rank in a blocking way"""
"""NOTE: `dst` is the local rank of the destination rank."""
Copy link
Contributor

Choose a reason for hiding this comment

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

high

While the change to 'blocking' is correct, the docstring format is unconventional and can be misleading. According to PEP 257, only the first string literal following a function definition is treated as its docstring. Subsequent string literals are simply statements that are evaluated and then discarded, having no effect.

To ensure the entire comment is recognized as the docstring by documentation tools and help(), it should be a single multi-line string.

Suggested change
"""Sends a tensor to the destination rank in a blocking way"""
"""NOTE: `dst` is the local rank of the destination rank."""
"""Sends a tensor to the destination rank in a blocking way.
NOTE: `dst` is the local rank of the destination rank.
"""

Comment on lines +785 to 786
"""Sends a tensor to the destination rank in a blocking way"""
"""NOTE: `dst` is the local rank of the destination rank."""
Copy link
Contributor

Choose a reason for hiding this comment

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

high

While the change to 'blocking' is correct, the docstring format is unconventional and can be misleading. According to PEP 257, only the first string literal following a function definition is treated as its docstring. Subsequent string literals are simply statements that are evaluated and then discarded, having no effect.

To ensure the entire comment is recognized as the docstring by documentation tools and help(), it should be a single multi-line string.

Suggested change
"""Sends a tensor to the destination rank in a blocking way"""
"""NOTE: `dst` is the local rank of the destination rank."""
"""Sends a tensor to the destination rank in a blocking way.
NOTE: `dst` is the local rank of the destination rank.
"""

@vllm-bot vllm-bot merged commit 7de45db into vllm-project:main Aug 3, 2025
16 checks passed
@andyxning andyxning deleted the update_doc_comment_for_send branch August 3, 2025 07:57
npanpaliya pushed a commit to odh-on-pz/vllm-upstream that referenced this pull request Aug 6, 2025
Signed-off-by: Andy Xie <andy.xning@gmail.com>
jinzhen-lin pushed a commit to jinzhen-lin/vllm that referenced this pull request Aug 9, 2025
Signed-off-by: Andy Xie <andy.xning@gmail.com>
Signed-off-by: Jinzhen Lin <linjinzhen@hotmail.com>
noamgat pushed a commit to noamgat/vllm that referenced this pull request Aug 9, 2025
Signed-off-by: Andy Xie <andy.xning@gmail.com>
Signed-off-by: Noam Gat <noamgat@gmail.com>
paulpak58 pushed a commit to paulpak58/vllm that referenced this pull request Aug 13, 2025
Signed-off-by: Andy Xie <andy.xning@gmail.com>
Signed-off-by: Paul Pak <paulpak58@gmail.com>
diegocastanibm pushed a commit to diegocastanibm/vllm that referenced this pull request Aug 15, 2025
Signed-off-by: Andy Xie <andy.xning@gmail.com>
Signed-off-by: Diego-Castan <diego.castan@ibm.com>
epwalsh pushed a commit to epwalsh/vllm that referenced this pull request Aug 28, 2025
Signed-off-by: Andy Xie <andy.xning@gmail.com>
zhewenl pushed a commit to zhewenl/vllm that referenced this pull request Aug 28, 2025
Signed-off-by: Andy Xie <andy.xning@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants