paper: launch_overhead_rust pins tokio 1.53.0 and patches crates to a local path
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rust
Research direction
Start with cutile-rs/cutile-benchmarks/paper/sec5_exp2_execution_mode_overhead/launch_overhead_rust/Cargo.toml and its Cargo.lock; the manifest’s local [patch.crates-io] paths currently point outside the checkout. Read the repository’s crate locations and adjust the patch paths so Cargo can load the workspace, then update tokio to 1.54.1 or another patched version. Done when the lockfile records a patched tokio version and the paper workspace resolves.
Written by the indexing model from the issue text.
Description
Summary
cutile-rs/cutile-benchmarks/paper/sec5_exp2_execution_mode_overhead/launch_overhead_rust/Cargo.lock pins tokio 1.53.0. That is below the patched line for RUSTSEC-2026-0386 (>=1.53.3 on the 1.53 series).
cargo update cannot rewrite the lock from this tree. The manifest's [patch.crates-io] points at /home/elibol/dev/cutile-rs/..., and those directories are not in the checkout. Cargo stops while loading cuda-async before it can move tokio.
Why this is separate
- #1619 bumps the locks Cargo can resolve. This one is not among them.
- #1620 / #1621 run
cargo denyoncutile-rs/Cargo.tomlonly. The paper workspaces stay out, and this manifest would not load under that check until the patches point at this tree. - No CI job builds
launch_overhead_rust. The paperrun.shscripts are the only callers, and they need those local paths.
Fix
Point the patches at the crates in this repository, then move tokio to 1.54.1 (or any >=1.53.3).
- Dominant language
- Rust
- Stars
- 3.8k
- Forks
- 325
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 64
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/cuda-rust
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NVIDIA/cuda-rust#1568 · 1 comment ·
Maintainers usually reply within 1 day
-
[BUG]: The doc of trait `LoadTileLike` is incorrectPossibly taken @akhil9tiet claimed this 11 days ago. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 72/100
NVIDIA/cuda-rust#1523 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
NVIDIA/cuda-rust#1303 · 1 comment ·
Maintainers usually reply within 1 day
All issues in NVIDIA/cuda-rust
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
haowjy/mars-agents#228 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
redlib-org/redlib#604 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dividebysandwich/rust-dos#240 ·
Maintainers usually reply within 1 day
-
A-UI C-Bug S-Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bevyengine/bevy#26330 ·
Maintainers usually reply within 2 days