monogosh throw ERR_INTERNAL_ASSERTION, caused by a Bug in Node.js

[Haseebullah9012]

Version

v20.11.0

Platform

Microsoft Windows NT 10.0.22621.0 x64

Subsystem

No response

What steps will reproduce the bug?

It got caused while running mongosh (MongoDB Shell) connection.
It eventually threw this error:

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

This is the first time.

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

No response

What do you see instead?

This is the Textual Error:

Atlas atlas-o5oa0d-shard-0 [primary] blog> node:internal/assert:14
    throw new ERR_INTERNAL_ASSERTION(message);
    ^

Error: 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

    at new NodeError (node:internal/errors:405:5)
    at assert (node:internal/assert:14:11)
    at internalConnectMultiple (node:net:1118:3)
    at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7) {
  code: 'ERR_INTERNAL_ASSERTION'
}

Node.js v20.5.1

Additional information

No response

[aduh95]

Duplicate of #51354.

Thanks for the report, we're aware of the issue, it has been fixed in the 21.x release line, and the fix should be included with 20.12.0.

[naveenjpr]

MongoDB Compass has encountered an unexpected error
Error [ERR_INTERNAL_ASSERTION]: 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
at new NodeError (node:internal/errors:406:5)
at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1118:3)
at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
at listOnTimeout (node:internal/timers:575:11)
at process.processTimers (node:internal/timers:514:7)

my node version v20.13.1