This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues

[Will956]

Version

20.11.0

Platform

x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

Don't know, looks like it happens after some timeouts

How often does it reproduce? Is there a required condition?

After some http timeouts

What is the expected behavior? Why is that the expected behavior?

No error

What do you see instead?

This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

Additional information

Stack trace:

at assert(node:internal/assert:14:10)
at internalConnectMultiple(node:net:1118:2)
at Timeout.internalConnectMultipleTimeout(node:net:1687:2)
at listOnTimeout(node:internal/timers:575:10)
at process.processTimers(node:internal/timers:514:6)

We followed this issue #50893, but looks like it's still present.

Thanks!

[marco-ippolito]

Duplicate of #51354