Test that close() exits when peer sends a RESET packet
Open
- Dominant language
- Rust
- Stars
- 40
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
While working on #98 there was no obvious way to confirm the behavior when a peer sends a RESET packet.
So:
- [ ] Add some mechanism that sends a RESET packet, on-demand
- [ ] Test that close() returns `ConnectionReset` if peer resets during transfer
Contributor guide
No contributing guide indexed for this repository
Research direction
Read issue #98 and the implementation of close(); then locate the existing transfer tests or packet-injection entry point. Add the on-demand RESET mechanism and verify that close() returns ConnectionReset when a peer resets during transfer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100