Skip to content

Conversation

bwasti
Copy link
Contributor

@bwasti bwasti commented Oct 6, 2025

Previous attempt to land #25769 caused CI failures because the version for flashinfer was not bumped.

Purpose

This PR tests and bumps a release candidate version of flashinfer.

Test Plan

Run CI

Test Result

[unknown]


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.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

@mergify mergify bot added the ci/build label Oct 6, 2025
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 bumps the version of flashinfer-python to 0.4.0rc2. My review highlights the risk of using a release candidate version for a dependency, which can affect stability. I also point out that the Dockerfile's flashinfer version has not been updated in sync with this change, as suggested by a code comment, which could lead to inconsistent behavior across different installation methods.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Comment on lines 715 to 719
], # Required for audio processing
"video": [], # Kept for backwards compatibility
# FlashInfer should be updated together with the Dockerfile
"flashinfer": ["flashinfer-python==0.3.1"],
"flashinfer": ["flashinfer-python==0.4.0rc2"],
# Optional deps for AMD FP4 quantization support

Choose a reason for hiding this comment

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

P1 Badge Keep Docker flashinfer version in sync

The change bumps the flashinfer extra to 0.4.0rc2, but the repo’s Dockerfile still installs flashinfer_python-0.3.1. The comment above this stanza explicitly says FlashInfer should be updated together with the Dockerfile, so Docker builds will continue to use the old wheel and miss the determinism fix this commit is targeting. Consider updating the pinned version in docker/Dockerfile to avoid version skew between local installs and the official image.

Useful? React with 👍 / 👎.

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.

Let's run the CI and see whether it works.
Please also fix the DCO issue

@yewentao256 yewentao256 added the ready ONLY add when PR is ready to merge/full CI is needed label Oct 6, 2025
@mgoin
Copy link
Member

mgoin commented Oct 6, 2025

Don't worry about DCO, we can force it to pass

@mgoin mgoin changed the title Bump flashinfer version to support determinism Bump flashinfer to 0.4.0rc2 to support determinism Oct 6, 2025
Signed-off-by: Bram Wasti <[email protected]>
@mgoin
Copy link
Member

mgoin commented Oct 7, 2025

@bwasti you forced pushed my dockerfile change out... so the dockerfile is still running with 0.3.1

@bwasti
Copy link
Contributor Author

bwasti commented Oct 7, 2025

sorry about the confusion here, I thought this was confirmed dead. (didn't realize I had overwritten your changes)

will close due to this effort: #26326

@bwasti bwasti closed this Oct 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/build 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.

3 participants