rust-lang / rust-lang/rust-playground
Check in a lockfile to continue building through yanked dependencies
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 267
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
We only generate and commit a Cargo.toml file, but as the crate graph gets larger, we are more and more likely to fail for a crate being yanked.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating where the repository generates and commits Cargo.toml, then inspect the surrounding build configuration for the appropriate Cargo.lock location and workflow. Check how the Rust Playground is built and verify that committing the lockfile allows builds to continue when a dependency is yanked; the change is done when the lockfile is checked in and the build succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100