TcpStream peer_addr failure response is always slower on Windows than on other platforms.
Open
Nobody has claimed this yet.
A-io
C-optimization
O-windows
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Test steps:
- crate a TcpStream connection
- Unplug the remote network cable
- Waiting for failed response
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
The issue names TcpStream::peer_addr but no source file or test. Reproduce the listed connection failure on Windows and compare its response timing with other platforms, then trace the platform-specific implementation. Done means the Windows failure response no longer exhibits the reported delay, with behavior covered by an appropriate regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100