- From: isonmad <notifications@github.com>
- Date: Fri, 16 Dec 2016 15:48:12 -0800
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 16 December 2016 23:48:46 UTC
> I think the exception is being propagated to the right place already If an error occurs in a transformstream that's part of a pipe chain, is the error not supposed to be propagated both backwards and forwards? Like I said in the OP, this makes propagating the error forward down the pipe chain from a transformstream impossible, in the current state of things. ```js const rs = getReadableStream(); const transformed = rs.pipeThrough(new TransformStream({}, new StrategyThatThrows())); const reader = transformed.getReader(); ``` If the intermediate TransformStream's strategy throws, it will propagate backwards and cancel `rs`, but `transformed` will just mysteriously hang and never receive any new chunks, because the writable end of the transformstream is errored and not doing anything anymore. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/628#issuecomment-267723600
Received on Friday, 16 December 2016 23:48:46 UTC