Use pipeline to propagate errors across all piped streams #288
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the inflater encounters an error, it is emitted on the parser stream. However, in a situation where there is an entry that has already been piped into the writable, the error will not be propagated there and the stream will remain stuck indefinitely. The suggested solution is to utilize the built-in
pipeline
utility from thenode:streams
module to effectively propagate errors across all streams in the pipe.