You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docIssues and PRs related to the documentations.duplicateIssues and PRs that are duplicates of other issues or PRs.netIssues and PRs related to the net subsystem.
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:399:5)
at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1077:3)
at afterConnectMultiple (node:net:1532:5)
The text was updated successfully, but these errors were encountered:
tniessen
added
duplicate
Issues and PRs that are duplicates of other issues or PRs.
net
Issues and PRs related to the net subsystem.
labels
Jun 3, 2023
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)
docIssues and PRs related to the documentations.duplicateIssues and PRs that are duplicates of other issues or PRs.netIssues and PRs related to the net subsystem.
Affected URL(s)
No response
Description of the problem
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:399:5)
at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1077:3)
at afterConnectMultiple (node:net:1532:5)
The text was updated successfully, but these errors were encountered: