René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"sockets can be undestroyed, confusing documentation","articleBody":"### Version\n\nv22.14.0\n\n### Platform\n\n```text\nMicrosoft Windows NT 10.0.26100.0 x64\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\n```js\nimport net from 'node:net';\nimport { once } from 'node:events';\n\nconst sock = new net.Socket();\nsock.on('connect', () => {\n   console.log('socket connected!');\n});\n\nsock.connect({ host: 'example.com', port: '80' });\nawait once(sock, 'connect');\n\nsock.destroy();\n\nsock.connect({ host: 'example.com', port: '80' });\n```\n\n### How often does it reproduce? Is there a required condition?\n\nReliably. Whether a socket is destroyed by manually calling `destroy()` or by an error (e.g. ECONNRESET).\n\n### What is the expected behavior? Why is that the expected behavior?\n\nThe expected behavior is that a socket which is destroyed never can be opened again. This is expected because the documentation says that \"no further data can be transferred\" after a stream is destroyed, and because both `Readable` and `Writable` draw a distinction between the \"closed\" and \"destroyed\" properties.\n\nsocket.destroy:\n> Ensures that no more I/O activity happens on this socket. Destroys the stream and closes the connection.\n\nsocket.destroyed:\n> Indicates if the connection is destroyed or not. Once a connection is destroyed no further data can be transferred using it.\n\n### What do you see instead?\n\nThe socket can be reopened after it is destroyed. The above code prints \"socket connected!\" twice.\n\n### Additional information\n\nI think we're likely stuck with the current behavior, but it should be *very* prominently documented.\n\nI think this also breaks the semantics of `Symbol.asyncDispose`, as inherited from the `Duplex` interface.","author":{"url":"https://github.com/rotu","@type":"Person","name":"rotu"},"datePublished":"2025-03-07T23:53:28Z","url":"https://github.com/nodejs/node/issues/57367"}