Re: [whatwg/streams] pipeTo: Read fulfilled after shutdown started (Issue #1207) from Tom Schuster on 2022-01-16 (public-webapps-github@w3.org from January 2022)

From: Tom Schuster <notifications@github.com>
Date: Sun, 16 Jan 2022 02:01:26 -0800
To: whatwg/streams <streams@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/streams/issues/1207/1013845090@github.com>

Thank you for investigating this! I certainly assumed it's possible, but had some trouble coming up with a test case myself. What I [came up with](https://gist.github.com/evilpie/fcbf5ea15440462fbbbfffd2c0e1a761) myself was using setTimeout and wasn't really reliable.

> Any chunks enqueued between those events will be dropped: the pipe will read them (because it hasn't yet released its reader), but will be unable to write them to the destination (because it's already errored).

That is exactly what I was concerned about. I don't really have any ideas on how to fix this myself. I guess we really don't want to wait on the last read as well?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/1207#issuecomment-1013845090
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/streams/issues/1207/1013845090@github.com>

Received on Sunday, 16 January 2022 10:01:39 UTC