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

Error [ERR_INTERNAL_ASSERTION] #49294

Closed
Jessemwangi opened this issue Aug 23, 2023 · 9 comments
Closed

Error [ERR_INTERNAL_ASSERTION] #49294

Jessemwangi opened this issue Aug 23, 2023 · 9 comments

Comments

@Jessemwangi
Copy link

Jessemwangi commented Aug 23, 2023

Version

20

Platform

Microsoft Windows 11 Pro

Subsystem

No response

What steps will reproduce the bug?

It happens when running strapi application with command npm run develop, during the normal operation of the app it will just break at some point.

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

frequent, when testing the application locally

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

No response

What do you see instead?

[2023-08-23 11:39:34.147] http: POST /admin/renew-token (7 ms) 200
[2023-08-23 11:39:34.161] http: GET /admin/init (6 ms) 200
[2023-08-23 11:39:34.244] http: GET /admin/telemetry-properties (54 ms) 200
[2023-08-23 11:39:34.357] http: GET /admin/information (88 ms) 200
[2023-08-23 11:39:34.377] http: GET /admin/users/me/permissions (102 ms) 200
[2023-08-23 11:39:34.440] http: GET /admin/users/me (55 ms) 200
[2023-08-23 11:39:34.514] http: GET /i18n/locales (66 ms) 200
[2023-08-23 11:39:34.739] http: GET /content-manager/init (34 ms) 200
[2023-08-23 11:39:34.923] http: GET /content-manager/content-types-settings (170 ms) 200
[2023-08-23 11:39:35.346] http: GET /content-manager/content-types/plugin::users-permissions.user/configuration (57 ms) 200
[2023-08-23 11:39:35.471] http: GET /content-manager/collection-types/plugin::users-permissions.user?page=1&pageSize=10&sort=username:ASC (73 ms) 200
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: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) {
  code: 'ERR_INTERNAL_ASSERTION'
}

Node.js v20.0.0

Additional information

No response

@mscdex
Copy link
Contributor

mscdex commented Aug 23, 2023

I believe this was already fixed in the latest version of node v20.x.

@Jessemwangi
Copy link
Author

the environment is v20.0.0

@mscdex
Copy link
Contributor

mscdex commented Aug 23, 2023

The latest version as of this writing is v20.5.1.

@fabricebircher
Copy link

fabricebircher commented Aug 26, 2023

node version: 20.5.1
-> FROM node:20.5.1-alpine@sha256:254989045b0555ee411cd8fe7bd8e3ae306fef34b4c9d5dfd020bdda86cdad97

uncaughtException: 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

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:405: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) 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:405: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)

@ShogunPanda
Copy link
Contributor

Can you please provide me a reproducible repro to handle this?
In alternative, I need to know which hosts your app was trying to connect to and how your DNS system resolved those.

@bnoordhuis
Copy link
Member

No follow-up, closing.

@bnoordhuis bnoordhuis closed this as not planned Won't fix, can't repro, duplicate, stale Sep 27, 2023
@ainsleyclark
Copy link

@Jessemwangi did you get this fixed?

@ShogunPanda
Copy link
Contributor

This is duplicate of #47644. Let's eventually continue there.

@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
None yet
Projects
None yet
Development

No branches or pull requests

6 participants