Alex Potsides

I think for this to work we need to be able to open ports with `SO_REUSEPORT`. This is [not currently supported](https://github.com/nodejs/node/issues/12228) by node.js but it appears to have [made it...

`reusePort` has been added to [server.listen](https://nodejs.org/docs/latest/api/net.html#serverlistenoptions-callback) as of node 23.1.0

I would strongly advise upgrading to the latest libp2p, we simply do not have the capacity to support older versions. There are [detailed migration guides](https://github.com/libp2p/js-libp2p/tree/main/doc/migrations) to make this as painless...

> in the it-ws library there are no calls to server.closeAllConnections() before close. I may be missing something but where is the `closeAllConnections` method defined? The `it-ws` module stores a...

> `http.Server` and `https.Server` has that method since NodeJs 18.2.0 Aha, that's interesting, nice find. The docs do say though: > This does not destroy sockets upgraded to a different...

Can you try adding [why-is-node-running](https://www.npmjs.com/package/why-is-node-running) to your script? It's invaluable at tracking down why node doesn't exit. ```js import why from 'why-is-node-running' // ... more imports async main() { try...

The `# KEYPAIRGENREQUEST` and `# SIGNREQUEST` stuff is safe to ignore - it's probably the `# ThreadSafeCallback callback` - it looks like a dial has hung and/or is still in...

> seems to only be happening with the WebRTC Direct transport Yeah, that's to be expected - the `ThreadSafeCallback` reference that's keeping the process running is part of WebRTCDirect (e.g....

I can't replicate this locally - what OS/node version are you using?

Thanks for that - I've replicated the issue locally. Can you try patching your local copy of `@libp2p/webrtc` in node_modules with the changes from https://github.com/libp2p/js-libp2p/pull/3076/files?w=1 ? It basically just wraps...