Encountered [ERR_INTERNAL_ASSERTION]

[lfaller-korrobio]

Hi all,

I encountered this issue while running the serverless framework. The error message asked me to submit an issue with the stack trace, although based on the output I get from serverless, it might be more appropriate to reach out to those folks instead.

Thanks for any pointers you might be able to provide!

$> serverless deploy --stage test --region us-east-1 --verbose
Running "serverless" from node_modules

Deploying NNN to stage test (us-east-1)

Packaging
Generated requirements from /Users/linafaller/repos/NNN/requirements.txt in /Users/linafaller/repos/NNN/.serverless/requirements.txt
Using static cache of requirements found at /Users/linafaller/Library/Caches/serverless-python-requirements/39c549dce1f9ab6975fc8c2ad425f64a0b8bfde238a94ccbd8b18bddf3a7cc70_x86_64_slspyc
Excluding development dependencies for service package
Injecting required Python packages to package
Layer psycopg2 is already uploaded.
Retrieving CloudFormation stack
Uploading
Skipped uploading psycopg2
Uploading CloudFormation file to S3
Uploading State file to S3
Skipped uploading psycopg2
Uploading service NNN.zip file to S3 (218.33 MB)
Recoverable error occurred (Socket connection timeout), sleeping for ~7 seconds. Try 1 of 4
✖ Uncaught exception
Environment: darwin, node 20.0.0, framework 3.31.0 (local) 3.30.1v (global), plugin 6.2.3, SDK 4.3.2
Credentials: Local, environment variables
Docs:        docs.serverless.com
Support:     forum.serverless.com
Bugs:        github.com/serverless/serverless/issues

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

[lfaller-korrobio]

I was able to get past this error by reducing the data in the current directory (so my upload to AWS Lambda was smaller). I believe this addresses the problem I faced and this issue can now be closed.

[tniessen]

Based on the stack trace I assume this is a duplicate of #47644.

[tniessen]

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

[ShogunPanda]

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.