Issue summary
from design doc:
fter investigation into the stream handlers, it looks like we do not currently support detection of EOF or ErrClosedPipe when reading from the stream, which we need to capture and propagate back to the networking stack to remove the peer from the peerset, and the peerViewSet.
Implementation details
- Capture
EOF or ErrrClosedPipe on any libp2p stream handler and propagate back to peerViewSet.
- On capture of these stream specific errors, the peer should be removed from the peerset.
Other information and links
Acceptance criteria
[] Peer should be removed from peerset when connection is determined to be terminated.
[] Unit test coverage of said sceneario.
Issue summary
from design doc:
Implementation details
EOForErrrClosedPipeon any libp2p stream handler and propagate back topeerViewSet.Other information and links
Acceptance criteria
[] Peer should be removed from peerset when connection is determined to be terminated.
[] Unit test coverage of said sceneario.