Bump nx to 0.11 (override Bumblebee's upstream constraint) - #50
Closed
ausimian wants to merge 1 commit into
Closed
Conversation
Bumblebee's pinned main commit (the latest upstream, as of this change) still declares `nx ~> 0.9.0 or ~> 0.10.0`, which blocks a straight dep bump. `override: true` on our `nx` requirement bypasses Bumblebee's constraint; its source happens to be compatible with 0.11 — the full conformance matrix (tiny-random + full-size Qwen3, ViT, Whisper, DistilBERT; fused kernels; MNIST training; quantised Qwen3) runs green under the bump. Drop the override once Bumblebee publishes past nx 0.10. axon 0.8.1 and scidata 0.1.11 remain pinned — the former is blocked the same way by Bumblebee, and the latter by its tightened castore 0.1 requirement that conflicts with tokenizers' castore 1.x.
Owner
Author
|
Abandoning — keeping emily's nx constraint at ~> 0.10 is fine; consumers can pin nx 0.11.x themselves, and this branch verified that works. |
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
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.
Summary
nxfrom 0.10 → 0.11. Bumblebee's pinnedmaincommit (which is also the current upstream HEAD) still declaresnx ~> 0.9.0 or ~> 0.10.0, sooverride: trueon our requirement is what actually unlocks 0.11. Bumblebee's source is compatible with 0.11 — the full test matrix runs green.RELEASE.mdunder## Changedwith a reminder to drop it once Bumblebee publishes past nx 0.10.axon 0.8andscidata 0.1.11deliberately left alone — axon is blocked by the same Bumblebee constraint, and scidata's newer versions tightencastore ~> 0.1which conflicts with tokenizers'castore 1.x.Test plan
mix precommit— 425 tests, 0 failuresmix test --include conformance --include qwen3_full --include qwen3_quant_full --include vit_full --include whisper_full --include distilbert_full --include training_full --include fast_kernels_full— 453 tests, 0 failures (tiny-random + full-size Qwen3, ViT, Whisper, DistilBERT; fused kernels; MNIST training; quantised Qwen3)mix compile --warnings-as-errorsunderMIX_ENV=test— clean