René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"quic: QuicStream writer creates unhandled error","articleBody":"I have currently a pattern, where the stream arrives with `onheaders`,\nand then after some processing I may answer with:\n```\n  stream.sendHeaders({ ':status': status.toString() })\n   stream.writer.endSync()\n```\nstatus is 404, the client on the other side (not a node.js client),\nthen errors the stream with code `256`\nand I get:\n```\nnode:internal/quic/quic:1009\n        error = makeQuicError(\n                ^\n\nQuicError: QUIC application error 256: stream reset with code 256\n    at Stream.onStreamClose (node:internal/quic/quic:1009:17) {\n  code: 'ERR_QUIC_APPLICATION_ERROR',\n  reason: 'stream reset with code 256'\n}\n```\nThis caused by the `drainWakeup` promise, here:\nhttps://github.com/nodejs/node/blob/a006c5dd12853b024b12aef22e2b331b9ea3d43c/lib/internal/quic/quic.js#L2316\n\nI wonder, if the user has to subscribe to some error to handle it.\nBut I think it is probably a problem how the writer interface is made here.\nThat is above my js skills.\n@jasnell @pimterry do one of you have an idea, if it is a problem inside node.js or on my code outside node.js\n","author":{"url":"https://github.com/martenrichter","@type":"Person","name":"martenrichter"},"datePublished":"2026-07-04T16:52:30Z","url":"https://github.com/nodejs/node/issues/64290"}