Environment
H3 Version:
h3@^2.0.1-rc.20 (but this is true for any version >= 2.0)
Deno Version:
deno 2.7.12
Reproduction
I set up a repro here
Describe the bug
When a client of an event stream running on h3 + deno closes the stream, an uncaught exception is thrown, because per WHATWG Streams, cancelling a TransformStream's readable errors its writable with the same reason. writer.closed therefore rejects with the string "resource closed".
I initially raised this bug with deno and their bot did an awesome write-up of what is happening and what a fix looks like. See denoland/deno#33166
I can open up a PR with the proposed fix as well. Locally, I verified already, that it does solve the uncaught exception.
Additional context
No response
Logs
Environment
H3 Version:
h3@^2.0.1-rc.20 (but this is true for any version >= 2.0)
Deno Version:
deno 2.7.12
Reproduction
I set up a repro here
Describe the bug
When a client of an event stream running on h3 + deno closes the stream, an uncaught exception is thrown, because per WHATWG Streams, cancelling a TransformStream's readable errors its writable with the same reason. writer.closed therefore rejects with the string "resource closed".
I initially raised this bug with deno and their bot did an awesome write-up of what is happening and what a fix looks like. See denoland/deno#33166
I can open up a PR with the proposed fix as well. Locally, I verified already, that it does solve the uncaught exception.
Additional context
No response
Logs