Skip to content

stream: throw instead of destroy? #33192

Closed
@rexagod

Description

@rexagod

I've come across multiple instances (in http2, for example) where due to a condition not being fulfilled, an error was thrown rather than destroying the stream itself (which would emit an error event and hence would be easier to work with).

I wanted to know if there's any reason behind not destroying the stream, or if this needs to be fixed?

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