You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. So, i was testing my app via Postman and then got error that server doesn't work then go to console and got this error message:
internal/assert.js: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 assert (internal/assert.js:14:11)
at ServerResponse.detachSocket (_http_server.js:223:3)
at resOnFinish (_http_server.js:684:7)
at ServerResponse.emit (events.js:311:20)
at onFinish (_http_outgoing.js:730:10)
at onCorkedFinish (_stream_writable.js:721:5)
at afterWrite (_stream_writable.js:528:5)
at afterWriteTick (_stream_writable.js:515:10)
at processTicksAndRejections (internal/process/task_queues.js:83:21) {
code: 'ERR_INTERNAL_ASSERTION'
}
I can't reproduse it again. Just open an issue as it says in the error message.
getting the same issue in nixos version 19 running a test with mocha:
Alltestspassed./project/test/node_modules/mocha/lib/runner.js:873throwerr;^Error[ERR_INTERNAL_ASSERTION]: ThisiscausedbyeitherabuginNode.jsorincorrectusageofNode.jsinternals.Pleaseopenanissuewiththisstacktrace at https://github.com/nodejs/node/issuesatassert(internal/assert.js:14:11)atprocess.target._send(internal/child_process.js:689:5)atprocess.<anonymous>(internal/child_process.js:646:12)atprocess.emit(events.js:323:22)atprocess.EventEmitter.emit(domain.js:482:12)atemit(internal/child_process.js:876:12)atprocessTicksAndRejections(internal/process/task_queues.js:85:21){code: 'ERR_INTERNAL_ASSERTION'}npmERR!Testfailed.Seeaboveformoredetails.
I am also getting this error in node 10 and node 12 via github actions which is running inside of a container that is not nixos. Strangely the same test works just fine in mac osx with no issues or errors so it does appear to be an interaction with linux or the mac version does not report the error.
node v12.16.1
the test does use express as a server.
not sure if this was fixed by this commit: f756c809e0
it looks like this is an issue on our side, I will update this comment when I know this for sure.
EDIT: For an future people that get this issue. The problem was a fire and forget style promise that was intentionally not being awaited. Does not seem to be related to node though, issue is with the mocha and the library being tested.
@verberden the error message alone won't be enough to know if it's an error in Node.js or on your side. The latter is very likely though. It is mostly an error thrown in case some internals are used in unsupported ways. Please check that again and open a new issue if it turns out to be an actual issue with Node.js, thanks!
Activity
rickyes commentedon Apr 21, 2020
Can you provide the code snippets used?
Puding07 commentedon Apr 23, 2020
I'm getting the same error when trying to run binary file created with nexe. (Just tried Proton-Native). I'm using Pop_OS! 19.10 and Node v12.16.1
aljones15 commentedon May 12, 2020
getting the same issue in nixos version 19 running a test with mocha:
I am also getting this error in node 10 and node 12 via github actions which is running inside of a container that is not nixos. Strangely the same test works just fine in mac osx with no issues or errors so it does appear to be an interaction with linux or the mac version does not report the error.
node v12.16.1
the test does use express as a server.
not sure if this was fixed by this commit: f756c809e0
it looks like this is an issue on our side, I will update this comment when I know this for sure.
EDIT: For an future people that get this issue. The problem was a fire and forget style promise that was intentionally not being awaited. Does not seem to be related to node though, issue is with the mocha and the library being tested.
BridgeAR commentedon May 23, 2020
@verberden the error message alone won't be enough to know if it's an error in Node.js or on your side. The latter is very likely though. It is mostly an error thrown in case some internals are used in unsupported ways. Please check that again and open a new issue if it turns out to be an actual issue with Node.js, thanks!
jfoclpf commentedon Feb 1, 2024
Anyone can tell me what most likely causes this error? On my side it seems lottery, sometimes it fails, others it doesn't