cameron314 / cameron314/readerwriterqueue
Assertion `!inSection && "Concurrent (or re-entrant) enqueue or dequeue operation detected (only one thread at a time may hold the producer or consumer role)
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.6k
- Forks
- 736
- Avg merge
- 10d 5h
- Merged PRs (30d)
- 1
Description
WHy is this issue coming. If it's lockfree the two threads even if they are trying to enqueue dequeue at the same time are expected synchronized
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
Start by reading the queue's single-producer, single-consumer contract and the assertion named in the issue title. Determine whether concurrent enqueue and dequeue calls violate the producer or consumer role assumptions; done means explaining the assertion's cause or providing a reproducible defect case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100