Add cache for zstd and lrzip checks
Open
Nobody has claimed this yet.
blocked ☹
whateverable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Commit a401e1da8df61ba6a93c5c233264730951c60345 added a few checks to make sure we get a useful message if zstd or lrzip are not installed. Problem is that these checks actually take ≈20ms which adds up to significant delays when doing some heavy lifting (e.g. in committable or bisectable). I think there's a way to do it by just slapping a once here and there, but I'm not sure.
Contributor 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.
Research direction
Inspect the zstd and lrzip checks introduced by commit a401e1da8df61ba6a93c5c233264730951c60345, then trace their use in the committable and bisectable paths. Confirm how missing tools are reported and ensure repeated checks are cached without losing that message or behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100