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

ERR_INTERNAL_ASSERTION #48075

Closed
TeachTeamHC opened this issue May 19, 2023 · 3 comments
Closed

ERR_INTERNAL_ASSERTION #48075

TeachTeamHC opened this issue May 19, 2023 · 3 comments
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs. net Issues and PRs related to the net subsystem.

Comments

@TeachTeamHC
Copy link

Version

v20.0.0

Platform

Linux 01fde54e-82c5-4aa9-9cb2-06068924540b 4.4.0-1104-aws #109-Ubuntu SMP Tue May 10 11:27:41 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

Every time we run a build (using nextjs SSG) on heroku, our data server crashes, showing the error below.

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

t

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

That our build pass without problems.

What do you see instead?

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:1106:3)
at Timeout.internalConnectMultipleTimeout (node:net:1637:3)
at listOnTimeout (node:internal/timers:575:11)
at process.processTimers (node:internal/timers:514:7)

Additional information

No response

@tniessen
Copy link
Member

Another duplicate of #47644.

@tniessen tniessen closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2023
@tniessen tniessen added the net Issues and PRs related to the net subsystem. label May 19, 2023
@tniessen
Copy link
Member

Please see #47644 (comment) for a potential workaround.

@tniessen tniessen added the duplicate Issues and PRs that are duplicates of other issues or PRs. label Jun 3, 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. net Issues and PRs related to the net subsystem.
Projects
None yet
Development

No branches or pull requests

3 participants