-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
Closed as not planned
Closed as not planned
Copy link
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.netIssues and PRs related to the net subsystem.Issues and PRs related to the net subsystem.
Description
Version
20.9.0
Platform
x86_64 x86_64 x86_64 GNU/Linux
Subsystem
aws 22.04.1-Ubuntu SMP
What steps will reproduce the bug?
i don't know
but i use some node_modues
pm2, mqtt, child_process
How often does it reproduce? Is there a required condition?
just once
What is the expected behavior? Why is that the expected behavior?
no any error
What do you see instead?
node:internal/assert:14
throw new ERR_INTERNAL_ASSERTION(message);
^
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) {
code: 'ERR_INTERNAL_ASSERTION'
}
Node.js v20.9.0
Additional information
I'm not sure it's my wrong or not, but at v10.24.1 & v18.12.1 never appeared
enBonnet, rawpixel-vincent, JungYeonHeo and nickthiru
Metadata
Metadata
Assignees
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.netIssues and PRs related to the net subsystem.Issues and PRs related to the net subsystem.