`net.TcpStream` always returns empty `ArrayBuffer` on disconnection
Open
Nobody has claimed this yet.
A-rt
bug
- Dominant language
- Rust
- Stars
- 54
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When the other end disconnects, TcpStream will continue yielding empty ArrayBuffers. This is probably wrong.
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 locating the net.TcpStream implementation and reproduce the behavior when the peer disconnects. Trace the stream's output after disconnection; done means it no longer continues yielding empty ArrayBuffers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100