A goroutine leak in manager/state/raft/transport/peer.go:430
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
Blocking Position:
https://github.com/moby/swarmkit/blob/8c19597365549f6966a5021d2ea46810099aae28/manager/state/raft/transport/peer.go#L430
How to reproduce:
You can reproduce the bug by goleak in the test function below.
https://github.com/moby/swarmkit/blob/8c19597365549f6966a5021d2ea46810099aae28/manager/state/raft/transport/transport_test.go#L129
The result is like this
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 at manager/state/raft/transport/peer.go:430, then inspect the reproduction in manager/state/raft/transport/transport_test.go:129. Run the test with goleak and trace the blocking position shown in the issue. Done means the reproduction no longer reports a leaked goroutine.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100