fix-lock-files check false negative
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5
- Forks
- 1
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 2
Description
This CI job should have failed: https://prow.fslabs.ca/view/s3/prow/pr-logs/pull/ForesightMiningSoftwareCorporation_fsl_libs/2003/cargo-tests/1980359858578264064
Now we have out of date lock files on main.
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 with the linked Prow log and find the CI implementation of the fix-lock-files check; inspect how it handles the out-of-date lock files reported on main. Done means the same stale-lock-file condition causes the CI job to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100