concourse / concourse/pool-resource
`get` on a pool resource should fail if named lock is unclaimed
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 59
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
The documentation says that get on a pool resource will get a "claimed" lock, but that is not the case. It will successfully fetch lock metadata even if the lock is in the unclaimed state.
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 by tracing the pool resource's get operation and how it handles the named lock's claimed and unclaimed states. Done means get rejects an unclaimed named lock while continuing to fetch metadata for a claimed lock; verify the behavior with the repository's relevant checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100