-
-
Notifications
You must be signed in to change notification settings - Fork 37.3k
Pipeline error causing stream #34842
Copy link
Copy link
Closed
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.streamIssues and PRs related to Node.js streams.Issues and PRs related to Node.js streams.
Description
Activity
Metadata
Metadata
Assignees
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.streamIssues and PRs related to Node.js streams.Issues and PRs related to Node.js streams.
Is your feature request related to a problem? Please describe.
Please describe the problem you are trying to solve.
Currently, there is no way to determine which stream in the pipeline function raised an error. In many cases, it would be helpful for the user, because they would get more insight as to what caused the error.
Describe the solution you'd like
Please describe the desired behavior.
PR 34 of the pump module was able to implement this.