concourse / concourse/pool-resource
Get behaviour does not match README
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 59
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Using Concourse 3.5.0 and the pool-resource we expected a 'get' to only return when an acquired lock was available. However, the behavior we see is that we are returned the latest resource version for the git repo backing the pool, regardless of a locks state.
The README for this resource states: in: Fetch an acquired lock.
Should the get behavior be to only get acquired locks, or get any lock?
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 README section stating that in fetches an acquired lock, then trace the resource's get behavior to compare it with the reported result for the pool's backing git repository. Confirm the intended semantics for acquired versus any locks, and make the behavior and documentation agree; no test or source path is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100