master: Cargo.lock is stale, so every PR fails Build at once under --locked

Open Beginner friendly
#2,191 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
build-system

Research direction

Start by comparing Cargo.lock with the project manifests and check the Build workflow to confirm where CI uses --locked. Regenerate the lockfile from the manifests, then verify the lockfile is current; done means the mismatch that makes Build fail before compilation is resolved.

Written by the indexing model from the issue text.

Description

Every pull request currently fails `Build` on all three platforms within seconds, before any project code compiles, because master's `Cargo.lock` no longer matches the manifests and CI passes `--locked`.

Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
21h 27m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from 1jehuang/jcode

All issues in 1jehuang/jcode

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.