Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`net.TcpStream` always returns empty `ArrayBuffer` on disconnection

Open
#70 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
networking

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.

Description

A-rt bug

When the other end disconnects, TcpStream will continue yielding empty ArrayBuffers. This is probably wrong.

Dominant language
Rust
Stars
54
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from y21/dash

All issues in y21/dash

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.