-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
Closed as not planned
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.
Description
Version
20.9.0
Platform
Linux exchange-deployment-7d6fd9f7f7-qw4tk 5.15.0-82-generic #91-Ubuntu SMP Mon Aug 14 14:14:14 UTC 2023 x86_64 Linux
Subsystem
lts-alpine
What steps will reproduce the bug?
It's hard to reproduce, I get this error since lts from the previous lts-alpine
Pleae find below the stack trace
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
How often does it reproduce? Is there a required condition?
From time to time (hour is the good time space) without specific triggered events.
What is the expected behavior? Why is that the expected behavior?
No Error
What do you see instead?
The stack trace described previously, then container restarts
Additional information
No response
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.