René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"stream/iter: push readable iterator.throw() resolves instead of rejecting","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\nconst { readable } = push();\nconst iterator = readable[Symbol.asyncIterator]();\nconst error = new Error('boom');\n\ntry {\n  const result = await iterator.throw(error);\n  console.log('resolved:', result);\n} catch (err) {\n  console.log('rejected:', err.message);\n}\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\n```console\nrejected: boom\n```\n\nThe spec says `Stream.push()` creates a readable whose composed pipeline is aborted “on return or throw (consumer stops iterating)” and cancellation is signaled to the writer. Since this is the iterator `throw()` path, the provided error should be propagated by rejecting with that error, not converted into a successful completion.\n\nSpec [§7.1](https://stream-iter.jasnell.me/#push-method), step 11\n\u003e On return or throw (consumer stops iterating), abort pipelineController and signal cancellation to writer.\n\n### What do you see instead?\n\n```console\nresolved: [Object: null prototype] { done: true, value: undefined }\n```\n\n\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-07-09T03:11:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/64378/node/issues/64378"}