NodeJS Crash AWS Lambda v20

[roybeitner]

Version

20

Platform

AWS Lambda

Subsystem

No response

What steps will reproduce the bug?

Not sure

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

No response

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

No response

What do you see instead?

{
    "errorType": "Error",
    "errorMessage": "This is caused by either a bug in Node.js or incorrect usage of Node.js internals.\nPlease open an issue with this stack trace at https://github.com/nodejs/node/issues\n",
    "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)"
    ]
}

Additional information

No response

[marco-ippolito]

What specific version are you using, AFAIK this bug has been fixed in a previous release @ShogunPanda

[roybeitner]

@marco-ippolito Node v20 on AWS Lambda, the runtime is Amazon Linux 23.

I don't know the exact version unfortunately, it's a serverless runtime managed by AWS.

[targos]

You can get the exact version inside the runtime with process.version.

[roybeitner]

Thanks @targos.
The version is v20.11.1 @marco-ippolito

[ShogunPanda]

@roybeitner This should have been fixed in 20.12.0. As soon as Lambda updates its runtime you should be good to go.
For the time being, you can prevent this by setting --no-network-family-autoselection in the NODE_OPTIONS environment variable.

[roybeitner]

Awesome, thanks all!
Closing for now.