Skip to content

[BugFix] Fix topk_softmax assert #19764

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ProExpertProg
Copy link
Collaborator

@ProExpertProg ProExpertProg commented Jun 17, 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.

Fix the assert (only compiled in debug mode) and change it to a TORCH_CHECK. Introduced in #18434.

Test Plan

CI

Test Result

(Optional) Documentation Update

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 @ProExpertProg, 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 bug by enhancing the robustness of the topk_softmax kernel. My change ensures that a critical input tensor's data type is validated at runtime across all build configurations, thereby improving the stability and reliability of the MoE (Mixture of Experts) component.

Highlights

  • Bug Fix & Runtime Safety: I've replaced a debug-only assert with a TORCH_CHECK in csrc/moe/topk_softmax_kernels.cu. This ensures that the type validation for topk_indices is performed at runtime in all builds (debug and release), preventing potential issues that might arise from incorrect tensor types in production.
  • Type Consistency: The TORCH_CHECK now explicitly validates that topk_indices is of at::ScalarType::Long. This change from at::ScalarType::Int64 aligns with common PyTorch type naming conventions for 64-bit integers, improving clarity and consistency.
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 configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

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 assertion in topk_softmax by replacing it with TORCH_CHECK and using at::ScalarType::Long, ensuring type validation in all builds.

@ProExpertProg ProExpertProg marked this pull request as ready for review June 17, 2025 18:34
@varun-sundar-rabindranath
Copy link
Contributor

Thanks for the fix @ProExpertProg 🙌

@robertgshaw2-redhat robertgshaw2-redhat enabled auto-merge (squash) June 17, 2025 23:02
@github-actions github-actions bot added the ready ONLY add when PR is ready to merge/full CI is needed label Jun 17, 2025
auto-merge was automatically disabled June 18, 2025 14:26

Head branch was pushed to by a user without write access

@DarkLight1337
Copy link
Member

Can you merge from main to see if the CI failures can be resolved?

Signed-off-by: Luka Govedic <[email protected]>
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants