Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node 20.9.0 - ERR_INTERNAL_ASSERTION since move from 18.x #50617

Closed
gchicoye opened this issue Nov 7, 2023 · 2 comments
Closed

Node 20.9.0 - ERR_INTERNAL_ASSERTION since move from 18.x #50617

gchicoye opened this issue Nov 7, 2023 · 2 comments
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs.

Comments

@gchicoye
Copy link

gchicoye commented Nov 7, 2023

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

@bnoordhuis
Copy link
Member

Known issue, duplicate of #50233 and other issues but cc @ShogunPanda just in case.

@bnoordhuis bnoordhuis closed this as not planned Won't fix, can't repro, duplicate, stale Nov 8, 2023
@bnoordhuis bnoordhuis added the duplicate Issues and PRs that are duplicates of other issues or PRs. label Nov 8, 2023
@ShogunPanda
Copy link
Contributor

This should have been fixed in #51045. Once it gets in 21.x or 20.x please let me know if you have additional problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs.
Projects
None yet
Development

No branches or pull requests

3 participants