TestFuzzCloseStream fails with leaked closed streams
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 37
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
=== RUN TestFuzzCloseStream
--- FAIL: TestFuzzCloseStream (0.05s)
multiplex_test.go:472: leaked closed streams
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 running TestFuzzCloseStream and inspect the failure at multiplex_test.go:472. Trace the test's stream-closing behavior to identify why closed streams remain leaked; done means the test passes without reporting leaked closed streams.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100