grandecola / grandecola/bigqueue
Acquire lock on file
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 454
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
This would ensure that the same bigueue is not operated on (written/read) by multiple processes/threads. https://linux.die.net/man/2/flock
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests; start by locating the bigqueue read and write entry points in the repository and read the linked flock documentation. Define how locking should cover operations across processes and threads, then verify that concurrent reads and writes to the same queue are prevented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100