diskusage calculation temporary locking a ref
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 50
Description
https://github.com/moby/buildkit/pull/861#issuecomment-471719419
Diskusage calculation (invoked by gc for example) takes a reference of a snapshot causing cache mounts to appear locked if they run at the same time and new cache mounts to be generated.
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 with the linked pull request comment and trace the diskusage calculation invoked by garbage collection. Inspect how it takes a snapshot reference while cache mounts run or new cache mounts are generated; done means diskusage no longer temporarily locks cache mounts or causes this conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100