René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Errors are not forwarded when using stream.duplexPair()","articleBody":"### Version\n\nv25.2.1\n\n### Platform\n\n```text\nLinux 6.17.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 24 Nov 2025 15:21:09 +0000 x86_64 GNU/Linux\n```\n\n### Subsystem\n\nstream\n\n### What steps will reproduce the bug?\n\nCreate a duplex pair and destroy one side with an error.\n\n```javascript\nimport stream from \"node:stream\";\n\nconst [ sideA, sideB ] = stream.duplexPair();\n\nsideA.on(\"error\", (err) =\u003e {\n    console.error(\"sideA error:\", err);\n});\n\nsideA.on(\"close\", () =\u003e {\n    console.log(\"sideA closed\");\n});\n\nsideA.resume();\n\nsideB.on(\"error\", (err) =\u003e {\n    console.error(\"sideB error:\", err);\n});\n\nsideB.on(\"close\", () =\u003e {\n    console.log(\"sideB closed\");\n});\n\nsideB.destroy(Error(\"Simulated error on sideB\"));\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\nI would expect on of the following outputs.\n\nIdeally:\n\n```\nsideB error: Error: Simulated error on sideB\n    at file:///duplex-pair-test.ts:23:15\n    at ModuleJob.run (node:internal/modules/esm/module_job:413:25)\n    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:654:26)\n    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5)\nsideB closed\nsideA error: Error: Simulated error on sideB\n    at file:///duplex-pair-test.ts:23:15\n    at ModuleJob.run (node:internal/modules/esm/module_job:413:25)\n    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:654:26)\n    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5)\nsideA closed\n```\n\nor\n\n```\nsideB error: Error: Simulated error on sideB\n    at file:///duplex-pair-test.ts:23:15\n    at ModuleJob.run (node:internal/modules/esm/module_job:413:25)\n    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:654:26)\n    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5)\nsideB closed\nsideA closed\n```\n\nThe latter would be what I see, if I created a TCP socket pair manually.\n\n### What do you see instead?\n\n```\nsideB error: Error: Simulated error on sideB\n    at file:///home/simon/projects/krevp/lib/new/duplex-pair-test.ts:23:15\n    at ModuleJob.run (node:internal/modules/esm/module_job:413:25)\n    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:654:26)\n    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5)\nsideB closed\n```\n\nsideA doesn't notice that sideB has errored or closed.\n\n### Additional information\n\nIn the provided minimal example the process also closes, as there are no pending tasks. If I keep it open via e.g. setInterval, still, no events on sideA.","author":{"url":"https://github.com/skadisch","@type":"Person","name":"skadisch"},"datePublished":"2025-12-10T11:31:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/61015/node/issues/61015"}