Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
4.3.0-rc1 causes sls deploy stucked
See original GitHub issueThe latest tag 4.3.0-rc1 makes sls deploy stucked in a loop.
strace shows infinite futex() syscall causing sls to stuck in 100% CPU usage.
Issue Analytics
- State:
- Created 5 years ago
- Comments:26 (11 by maintainers)
Top Results From Across the Web
Querying stack state before sls deploy to avoid failures due to ...
Hey there, We're using serverless for our CI process, and a common issue we have is that if we push 2 commits to...
Read more >How to debug serverless deploy - hangs during packaging
In .serverless folder I can see services being zipped fine except the one that is using puppeteer . If I do sls package...
Read more >Top 10 Serverless Deployment Errors (and How to Fix Them)
The cause: This situation often arises when a deployed stack's subsequent deployment fails, along with the stack rollback or deletion. Deletes ...
Read more >Troubleshoot deployment issues in Lambda
When you deploy updates to your function directly with the Lambda API or with a client such as the AWS CLI, you can...
Read more >stuck at cloudformation update in progress : r/serverless - Reddit
I'm trying to deploy a yaml file, and I'm stuck at updating in progress, looking at the stack i can see that the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks, guys! I could reproduce it with @gs-jackal repo.
The problem was caused by a combination of https://github.com/serverless/serverless/pull/3911 and https://github.com/serverless/serverless/issues/2631. Basically, serverless doesn’t resolve options properly and doesn’t resolve variables at constructor time. Inferring the stage and region at constructor time was causing an endless loop within serverless for some reason (maybe I should just create a ticket in serverless about it since it should error and never go into endless loops no matter what).
Can you try 4.3.3-rc.1 and see if the issue is resolved?
Thanks @juanjoDiaz , works great now!