[None][chore] Update flashinfer-python from 0.6.11.post1 to 0.6.12rc1 - #14512
Conversation
Bump flashinfer-python dependency to the v0.6.12rc1 release candidate. The wheel is not yet published to PyPI, so requirements.txt pins to the GitHub tag via a git+https URL. Updated version pins in requirements.txt, security_scanning/pyproject.toml, and ATTRIBUTIONS-Python.md. Signed-off-by: yihwang-nv <yihwang@nvidia.com>
|
/bot run --disable-fail-fast --add-multi-gpu-test |
📝 WalkthroughWalkthroughThis PR updates the ChangesDependency Version Upgrade
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@requirements.txt`:
- Line 57: Replace the mutable tag in the requirements entry for
flashinfer-python with the full commit SHA to ensure reproducible installs:
locate the line containing "flashinfer-python @
git+https://github.com/flashinfer-ai/flashinfer.git@v0.6.12rc1#egg=flashinfer-python"
and change the ref after the @ to the immutable commit
"529e592e9d8c5677b25c3cb38358bbd4def6c6dd" so it reads the same URL but with
"`@529e592e9d8c5677b25c3cb38358bbd4def6c6dd`" instead of "`@v0.6.12rc1`".
In `@security_scanning/pyproject.toml`:
- Line 57: The pyproject pin for the dependency "flashinfer-python
(==0.6.12rc1)" is out of sync with the lockfile which still records
0.6.11.post1; regenerate or update the lockfile so both declare the same
version: either change the pyproject constraint to match the lockfile or run the
dependency manager's lock/update command to produce a poetry.lock that contains
flashinfer-python==0.6.12rc1, then commit the updated lockfile to ensure
scanners read consistent metadata.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: fb28b5ac-7611-4a92-b5d3-88c272aa7e47
📒 Files selected for processing (3)
ATTRIBUTIONS-Python.mdrequirements.txtsecurity_scanning/pyproject.toml
|
PR_Github #50142 [ run ] triggered by Bot. Commit: |
|
PR_Github #50142 [ run ] completed with state
|
|
/bot run --disable-fail-fast --add-multi-gpu-test |
|
PR_Github #50226 [ run ] triggered by Bot. Commit: |
|
PR_Github #50226 [ run ] completed with state
|
|
/bot run --disable-fail-fast --add-multi-gpu-test |
|
PR_Github #50234 [ run ] triggered by Bot. Commit: |
|
PR_Github #50234 [ run ] completed with state |
…NVIDIA#14512) Signed-off-by: yihwang-nv <yihwang@nvidia.com>
|
This change will block next week's release. cause: |
I have update flashinfer-python to 0.6.12rc2 #14607. This issue may has been resolved. |
Summary
requirements.txtpins to the GitHub tag viagit+https://github.com/flashinfer-ai/flashinfer.git@v0.6.12rc1requirements.txt,security_scanning/pyproject.toml, andATTRIBUTIONS-Python.mdsecurity_scanning/poetry.lockintentionally left untouched (RC has no PyPI hashes); maintainers regenerate it separatelyTest plan
pip install -r requirements.txtinstalls successfully (requires building flashinfer from source)pytest tests/unittest/_torch/flashinfer/ -vpytest tests/unittest/_torch/attention/test_flashinfer_attention.py -vSummary by CodeRabbit