-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrading from 2.44.3 to 2.45.0 causes deployment failure #32
Comments
@leanderiversen I ran into this and tracked down the issue. The problem arises from cthackers/adm-zip#548. I was able to fork this repo, pin adm-zip at 0.5.14, build sst, and patch my repo's version of sst 2.47.0 with the rebuilt version of support/custom-resources/index.mjs. A little complicated but it does fix the problem! If I have some more time I'll put up a PR. |
Hello, |
@Gr33nLight I do not know of another solution besides what I described yet, no. https://github.com/SmooAI/sst-v2 There is my fork for the record. There's an open PR that should fix it if the SST team merges and releases - #34 |
Thanks, I can't use a forked version of sst at the moment but I'm hoping it gets merged soon. |
Released in v2.47.1 |
Still getting the same error with v2.47.1 Looks like this from @brentrager's fork could be the fix? |
I have not had this specific issue happen since |
I had the same issue. Patching this change through pnpm allowed me to deploy again. |
I have run in to the same issue, I have just done a major upgrade of Next from 14 to 15 and with that upgraded SST too. My current versions are
I have confirmed the version of
I am struggling to tease out the underlying cause. There is mention of timing out. The file in question is around 50MB and I have checked the bucket, there are plenty of much larger files uploaded. |
In the end, I got everything working again using
|
Hi,
We are currently running our website using
SST 2.44.3
andOpenNext 3.1.3
, and would like to upgrade to the latest V2 version of SST. After debugging this as best as I can, I have found that the upgrade from2.44.3
to2.45.0
or above causesUPDATE_FAILED Received response status [FAILED] from custom resource. Message returned: socket hang up
forsite/defaultServerFunction/AssetReplacer Custom::AssetReplacer
andsite/RevalidationProvider/framework-onEvent AWS::Lambda::Function
.We have also tried a combination of the latest V2 versions of SST and OpenNext to see if would play nice, but it does not seem like the case.
Do you have any ideas as to why this is happening?
Thank you!
The text was updated successfully, but these errors were encountered: