Skip to content

Dropping Endpoint causes unexpected streams behaviour #3170

Description

@SanjoDeundiak

Problem:

Currently, after dropping the Endpoint the following is observed:

  • tx operations succeed
  • rx operations never return from an .await

This is concerning because Endpoint drop can happen particularly
due to IO implementation returning an error, which makes the current
behaviour unexpected and hard to handle.

The expected behaviour is:

  • tx operations return an error
  • rx operations return an error

Solution:

Close all streams on Endpoint drop

  • Does this change what s2n-quic sends over the wire? --> No
  • Does this change any public APIs? --> No

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions