René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"stream/iter: push writer.end() resolves before readable drains buffered data","articleBody":"### Version\n\n26.2.0\n\n### Platform\n\n```text\nmacOS 26.5.0\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 { writer, readable } = push();\nwriter.writeSync('hello');\nconst events = [];\n\nwriter.end().then(() =\u003e {\n  events.push('end resolved');\n});\n\nawait Promise.resolve();\n\nevents.push('after microtask');\nfor await (const _ of readable) {\n  events.push('readable drained');\n}\nconsole.log(events);\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\n[ 'after microtask', 'readable drained', 'end resolved' ]\n```\n\n`writer.end()` should stay pending until the readable drains, so end resolved should appear after readable drained.\n\n### What do you see instead?\n\n```console\n[ 'end resolved', 'after microtask', 'readable drained' ]\n```\n\n`writer.end()` currently resolves before the readable side consumes the buffered `\"hello\"` chunk\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-05-23T05:58:51.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/63502/node/issues/63502"}