René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"stream/iter: Writer.end() ignores AbortSignal","articleBody":"### Version\n\nmain\n\n### Platform\n\n```text\nmacOS 26.5.2\n```\n\n### Subsystem\n\nstream\n\n### What steps will reproduce the bug?\n\n```js\nimport { push } from 'node:stream/iter';\n\nasync function repro(label, abortBeforeEnd) {\n  const { writer, readable } = push();\n  await writer.write('x');\n\n  const controller = new AbortController();\n  if (abortBeforeEnd) controller.abort(new Error('stop'));\n\n  const ending = writer.end({ signal: controller.signal }).then(\n    (bytes) => `resolved: ${bytes}`,\n    (error) => `rejected: ${error.message}`,\n  );\n\n  if (!abortBeforeEnd) controller.abort(new Error('stop'));\n\n  const draining = (async () => {\n    for await (const chunk of readable) {\n      void chunk;\n    }\n  })();\n\n  console.log(`${label}: ${await ending}`);\n  await draining;\n}\n\nawait repro('pre-aborted', true);\nawait repro('aborted while draining', false);\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways\n\n### What is the expected behavior? Why is that the expected behavior?\n\nit should reject with the signal’s abort reason in both cases.\n\n### What do you see instead?\n\n```console\npre-aborted: resolved: 1\naborted while draining: resolved: 1\n```\n\n`end()` resolves successfully whether the signal is already aborted or becomes aborted while the buffered data is draining.\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-07-25T02:38:26Z","url":"https://github.com/nodejs/node/issues/64726"}