Repository navigation
docs(cuda-oxide): update remaining nightly references and doctor check for 1.99.1 - #1617
Merged
nihalpasham merged 4 commits intoOct 23, 2026
Merged
Conversation
…k for 1.99.1 - Update the root `README.md`, umbrella `docs/index.md`, `building-from-source.md`, `error-handling-and-debugging.md`, crate READMEs (`cargo-oxide`, `cuda-oxide-codegen`, `cute-rs`, `ctm-rs`, `cute-layout`), workspace manifests, and CI/script comments to describe the pinned stable `1.99.1` toolchain rather than a nightly pin. - Update `cargo oxide doctor` (`doctor.rs`) so step 1 checks `rustc --version` without requiring the string `"nightly"` (step 2 already verifies the active toolchain against `rust-toolchain.toml`). Signed-off-by: nihalpasham <nihalp@nvidia.com>
nihalpasham
requested review from
binarybana,
elibol,
kkraus14 and
rparolin
as code owners
October 23, 2026 07:40
Every cute-rs README that runs a CuTeDSL comparison now gives the same three-line setup: install the CUTLASS compiler, create cute-rs-preview/.venv, and install cute-rs-preview/requirements.txt. The per-example requirements files include the shared one, so the DSL 4.7.0 family (SM120a prefill and decode, SM100 FMHA prefill, SM100 MLA decode, fp16_gemm) shares a single environment. The blockscale references keep their own pins. The runners agree on where to look: --python where it exists, CUDA_OXIDE_CUTE_PYTHON, the example's .venv, the shared cute-rs-preview/.venv, then python3. The SM100 runners no longer fall back to the fp16_gemm venv, and fp16_gemm's automatic setup creates the shared environment instead of a local one. Each comparison script checks for numpy, torch, cutlass and cuda before any GPU work and prints the setup commands when they are missing, instead of a traceback after the Rust build. The Rust-only READMEs name the `cargo oxide toolchain install cutlass` step inline, and the devcontainer installs python3-venv so the setup works there. Signed-off-by: nihalpasham <nihalp@nvidia.com> Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
nihalpasham
force-pushed
the
docs/fix-remaining-nightly-references
branch
from
October 23, 2026 08:50
54c775a to
4f41232
Compare
2.14.1 is what a fresh install resolves today and runs the SM120a comparisons. The recorded B200 results used 2.13.0+cu130; the SM100 reference notes keep that record. Signed-off-by: nihalpasham <nihalp@nvidia.com> Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ntu-26.04 GitHub Actions migrated `ubuntu-latest` to `ubuntu-26.04`, and NVIDIA's `developer.download.nvidia.com/compute/cuda/repos/ubuntu2604/x86_64` repository only publishes CUDA 13.3 and 13.4 (`cuda-nvcc-13-3`, `cuda-nvcc-13-4`). Requesting `cuda: "13.1.1"` caused `apt` to miss NVIDIA's CDN and fall back to Ubuntu's regional `resolute/multiverse` mirror (`http://azure.archive.ubuntu.com`), which times out in `westus3` and stalls toolkit installation for >70 minutes. Bump `Jimver/cuda-toolkit` to `v0.2.36` (`0ca15bb027...`) and `cuda` to `13.3.1` across `clippy.yml`, `docs.yml`, `examples-compile.yml`, and `unit-tests.yml` so `apt` pulls CUDA packages directly from NVIDIA's global CDN on both `ubuntu-24.04` and `ubuntu-26.04`. Signed-off-by: nihalpasham <nihalp@nvidia.com>
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
Update remaining references to a pinned
nightlytoolchain across the rootREADME.md, umbrelladocs/index.md,cuda-oxide-book, crate READMEs, and comments, and fixcargo oxide doctorstep 1 so it does not reject stablerustc 1.99.1:Changes
README.md,docs/index.md,Cargo.toml,rust-toolchain.toml):Pinned nightlytoPinned stable Rust (1.99.1), managed by cargo oxide.cuda-oxidebook & crate READMEs:appendix/building-from-source.md,gpu-programming/error-handling-and-debugging.md,crates/cargo-oxide/README.md,crates/cuda-oxide-codegen/README.md, andcute-rs-preview/{cute-rs,ctm-rs,cute-layout}/README.md.cargo oxide doctor(crates/cargo-oxide/src/commands/doctor.rs,src/backend.rs):version.contains("nightly")gate indoctorstep 1 (step 2'sdoctor_report_toolchain_pinalready checks that the active toolchain matchesrust-toolchain.tomland has all required components), and update the mismatch string inbackend.rs.cuda-oxide/Cargo.toml,rustc-codegen-cuda/Cargo.toml,cuda-host/src/lib.rs,cuda-oxide-codegen/src/lib.rs, CI workflows, and scripts):Validation
cargo run -p cargo-oxide -- doctorcargo test -p cargo-oxidejust fmt-checkjust check-guardsjust bookChecklist
git commit -s)Python reference environment (cute-rs examples and models)
One setup for every CuTeDSL comparison, the same three lines in each README:
cute-rs-preview/requirements.txt: shared pins for the DSL 4.7.0 family; the per-examplerequirements.txtfiles include it. The blockscale references keep their own DSL pins.--pythonwhere it exists,CUDA_OXIDE_CUTE_PYTHON, the example's.venv, the sharedcute-rs-preview/.venv, thenpython3. The SM100 runners no longer look for the fp16_gemm venv; fp16_gemm's automatic setup now creates the shared environment.compare.pychecks fornumpy,torch,cutlassandcudabefore any GPU work and prints the setup commands instead of a traceback after the Rust build.cargo oxide toolchain install cutlass. The devcontainer installspython3-venv.Validation:
cargo fmt --check,cargo clippy --all-targets -- -D warningsandcargo testfor the three edited example crates;python3 -m unittest public_reference.test_setup; the status-guard scripts.