potential race condition in stream reading loop
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 37
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
See PR description of https://github.com/libp2p/go-mplex/pull/114.
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 description of PR #114, which the issue identifies as the source of the race-condition details. Then trace the stream reading loop and determine how the concurrent access can be reproduced and verified; done means the race is resolved and the relevant behavior is covered by the project's tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100