sst: `sst dev` stuck during deployment and cleanup
Describe the Bug
When running sst dev, the deployment process starts normally, but after some time, it gets stuck indefinitely. The process does not complete, and attempting to exit results in the "Cleaning up..." message hanging indefinitely, requiring a forced kill.
Subsequent attempts to run sst dev skip previously deployed resources but remain stuck at the beginning. The same behavior is observed with sst refresh and sst remove.
I have retried multiple times, and at least two attempts completed successfully, but I have no idea why—it didn’t seem to be tied to any specific changes in my setup.
Expected Behavior
The sst dev command should complete the deployment process successfully or fail with an explicit error message instead of hanging indefinitely.
Steps to Reproduce
- Run
sst dev. - Observe that deployment starts normally but eventually gets stuck indefinitely.
- Try to exit the process, but it remains stuck at
"Cleaning up...". - Kill the process and retry
sst dev—it skips some steps but remains stuck. - The same issue occurs when running
sst refreshorsst remove. - At least two attempts eventually succeeded, but I couldn’t identify a pattern for why.
Logs and Screenshots
- SST Logs: The only logs observed are periodic logs every minute, with no errors or indications of failure.
- Pulumi Logs: Shows only
"Updating..."without further details.
Environment Details
- SST Version:
3.7.9(also tested with the latest version, same issue) - Node.js Version:
22.14.0 - npm Version:
10.9.2 - Operating System: macOS Ventura 13.5 (MacBook Pro M1)
Additional Information
- Other developers working on the same project do not face this issue.
- The issue seems specific to my local environment or configuration.
- The fact that at least two attempts were successful suggests it might be an intermittent issue, but I couldn’t determine the cause.
Would appreciate any insights on potential causes or solutions!
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 1
- Comments: 19 (7 by maintainers)
did this from my project and that seemed to have fixed it, not sure what caused that behaviour though