Upgrade drjax to 0.2.1 - #5075
Open
khatwanimohit wants to merge 1 commit into
Open
Conversation
khatwanimohit
requested review from
SurbhiJainUSC,
bvandermoon,
darisoy,
igorts-git,
parambole,
richjames0 and
shralex
as code owners
August 31, 2026 19:25
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
khatwanimohit
force-pushed
the
upgrade-drjax-0.2.1
branch
from
August 31, 2026 19:49
b8e122d to
74373c1
Compare
SurbhiJainUSC
approved these changes
Aug 31, 2026
khatwanimohit
force-pushed
the
upgrade-drjax-0.2.1
branch
2 times, most recently
from
August 31, 2026 22:30
a68877c to
cd579d3
Compare
khatwanimohit
requested review from
gobbleturk,
huytransformer and
xibinliu
as code owners
August 31, 2026 22:30
Bump the drjax floor to the latest PyPI release in the base requirements and regenerate the generated_requirements/ locks with the seed-env flow from docs/development/update_dependencies.md. Regenerating re-resolves each lock in full, so the locks also pick up unrelated version bumps. Pins llguidance<1.8.0 in the post-training base requirements: seed-env cannot resolve that lock otherwise, since vllm's tpu.txt constrains llguidance to <1.8.0 while the previously unpinned entry resolved to >=1.8.0. That break is independent of drjax and reproduces on main. Regenerating also moves tokamax to 0.0.13, which imports xprof at module scope. xprof is filtered out of the decoupled requirements because it depends on gcsfs and google-cloud-storage, and maxtext imports tokamax from megablox, so every decoupled test that reaches maxtext.layers.moe stopped collecting, and letting xprof back in would make the Google Cloud clients importable in the one environment meant to prove they are absent. Pin tokamax==0.0.12 for the decoupled requirements only, via a new PINNED_PACKAGES map in generate_decoupled_requirements.py. 0.0.12 is the last release that does not need xprof, so that environment stays free of the Cloud clients while the hardware locks keep tokamax 0.0.13.
khatwanimohit
force-pushed
the
upgrade-drjax-0.2.1
branch
from
September 1, 2026 03:35
cd579d3 to
bde759a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Bump the drjax floor to the latest PyPI release
Notice 1: Once all tests pass, the "pull ready" label will automatically be assigned.
This label is used for administrative purposes. Please do not add it manually.
Notice 2: For external contributions, our settings currently require an approval from a MaxText maintainer to trigger CI tests.
Tests
CI
Checklist
Before submitting this PR, please make sure (put X in square brackets):
gemini-reviewlabel.