Uncaught Exception: This is caused by either a bug in Node.js or incorrect usage of Node.js internals

[juliusmarminge]

Version

20.x (20.11.1 as per https://vercel.com/changelog/node-js-v20-lts-is-now-generally-available)

Platform

Vercel Node.js 20 Lambda function

Subsystem

No response

What steps will reproduce the bug?

This is the tricky part - idk...

I've never gotten it locally, only deployed on Vercel, so maybe it's AWS Lambda related... I really couldn't tell.

This is the repo: https://github.com/juliusmarminge/trellix-trpc deployed here: https://trellix-trpc.vercel.app/

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

It's happening like 3 times an hour in prod

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

no error - better stack trace would also be nice to see further down what caused this exception

What do you see instead?

errorMessage:
"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",...
code:
"ERR_INTERNAL_ASSERTION",...
stack:
[
"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 (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)"...
]

From my observability platform:

Additional information

No response

[juanarbol]

Thanks for the report. Do you have a minimal repro case? That would be a bit more helpful than reading a whole repo

[Linkgoron]

Looking at the stack trace, I think that this was recently fixed here:

#51045

So, the fix is in node 20.12.0

[aduh95]

It looks like the underlying issue has already be fixed in the latest version. Closing for now, we can reopen if you're able to reproduce with 20.12.0 or later.

[juliusmarminge]

Thanks! Will see when Vercel updates to 20.12 if it's fixed 👍🏼