Skip to content

Support detection of EOF and ErrClosedPipe in current network stream #4802

@timwu20

Description

@timwu20

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-implementationthis issue/pr is a new feature or functionality.

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions