Skip to content

Conversation

@Josephasafg
Copy link
Contributor

@Josephasafg Josephasafg commented Aug 13, 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

With the work on V1 on both mamba models (1 and 2) we need to have a distinction in the file names to better understand which is which. In the past mamba1 wasn't available in V1, now that it is, mamba_attn.py which was for mamba2 should be renamed to mamba2_attn.py for clarity and distinction.

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

🚀

@Josephasafg
Copy link
Contributor Author

@tdoublep @heheda12345 Can you please review? Thanks

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 is a refactoring that renames vllm/v1/attention/backends/mamba_attn.py to vllm/v1/attention/backends/mamba2_attn.py. This change improves clarity by explicitly distinguishing the Mamba v2 attention backend from the Mamba v1 implementation, which is a welcome improvement for code maintainability. All corresponding import paths have been updated correctly across the codebase. The changes are consistent and well-executed. I find no issues of high or critical severity.

@mergify mergify bot added the v1 label Aug 13, 2025
Copy link
Member

@tdoublep tdoublep left a comment

Choose a reason for hiding this comment

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

LGTM - thanks

Copy link
Member

@yewentao256 yewentao256 left a comment

Choose a reason for hiding this comment

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

Looks good to me, thanks for the work!

@yewentao256 yewentao256 added the ready ONLY add when PR is ready to merge/full CI is needed label Aug 13, 2025
@Josephasafg
Copy link
Contributor Author

@yewentao256 I think CI is failing unrelated to my changes. Can you please help with force push maybe?

Copy link
Collaborator

@heheda12345 heheda12345 left a comment

Choose a reason for hiding this comment

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

LGTM!

@heheda12345
Copy link
Collaborator

The CI is in a very bad status. Therefore, the main branch is frozen and only accepts force merge related to CI fix now.

@Josephasafg
Copy link
Contributor Author

@heheda12345 can this be merged now? I believe the failing test is unrelated

@heheda12345
Copy link
Collaborator

Can you rebase with main branch again? The tree eagle failure is fixed on main.

@Josephasafg
Copy link
Contributor Author

@heheda12345 Updated, thanks

@heheda12345 heheda12345 enabled auto-merge (squash) August 15, 2025 06:30
@heheda12345 heheda12345 merged commit 3d232db into vllm-project:main Aug 15, 2025
45 checks passed
yiliu30 pushed a commit to yiliu30/vllm-fork that referenced this pull request Aug 19, 2025
divakar-amd pushed a commit to divakar-amd/vllm_upstream that referenced this pull request Aug 20, 2025
djmmoss pushed a commit to djmmoss/vllm that referenced this pull request Aug 21, 2025
epwalsh pushed a commit to epwalsh/vllm that referenced this pull request Aug 28, 2025
xiao-llm pushed a commit to xiao-llm/vllm that referenced this pull request Aug 28, 2025
zhewenl pushed a commit to zhewenl/vllm that referenced this pull request Aug 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

5 participants