Parallelize leeway vet
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
leeway vey is currently not parallelised which makes it quite slow - too sow to run as a pre-commit hook. In a gitpod-io/gitpod workspace time leeway vet currently takes about 9s
Let us parallelize it and see how fast we can get it 🐎
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
Start at the leeway vet entry point and measure the current roughly 9-second runtime in a gitpod-io/gitpod workspace. Trace how vet work is scheduled, then verify that it runs in parallel, preserves the existing vet results, and improves the pre-commit-hook runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, performance, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100