https://serverless-stack.com/ logo
#sst
Title
# sst
d

Dan Suceava

05/30/2022, 9:44 PM
I recently upgraded to 1.0.2, then to 1.2.11, and I started getting these errors randomly while deploying:
fail: One or more of the specified parts could not be found.  The part may not have been uploaded, or the specified entity tag may not match the part's entity tag.
... I'll get the errors once, then re-deploy and no errors, then next time this error again ... I've tried downgrading back to 1.0.2 and still getting them, so not sure what's causing these ... I'm not even sure it's related to the upgrade. Has anyone seen these?
t

thdxr

05/30/2022, 9:45 PM
this is with
sst deploy
?
d

Dan Suceava

05/30/2022, 9:45 PM
yes
t

thdxr

05/30/2022, 9:46 PM
it looks like in the upload step where cdk uploads all assets to aws, some parts of it are failing. hm
are people even supposed to be seeing these progress bars @Frank? I feel like I don't recognize it
have you tried wiping your
.build
folder?
d

Dan Suceava

05/30/2022, 9:47 PM
I don't think I ever see the progress if it succeeds, only see it when it fails
I did not try wiping that folder, will try
f

Frank

05/30/2022, 9:47 PM
it’s only printed if
--verbose
is on
d

Dan Suceava

05/30/2022, 9:48 PM
I don't have verbose on 🤔
f

Frank

05/30/2022, 9:48 PM
by looking at the progress, it seem @Dan Suceava have ~50 lambda functions 😏
d

Dan Suceava

05/30/2022, 9:49 PM
yeah
f

Frank

05/30/2022, 9:49 PM
it seems to be an error coming from S3 when CDK tried to upload the function zips to S3
d

Dan Suceava

05/30/2022, 9:56 PM
on each deploy it uploads a new zip for each function, correct? there's no dependency on any existing files on S3, is there? I ask because I also happened to run the ToolkitCleaner the first time a couple of days ago, but didn't think that would affect new deploys
f

Frank

05/30/2022, 9:59 PM
it shouldn’t.. if the issue persistent, try emptying the CDK bucket in S3, and see if that helps
The bucket is named like
cdk-xxxxxxxx-assets-1234567890-us-east-1
d

Dan Suceava

05/31/2022, 3:26 PM
@Frank I emptied the bucket, and still no luck ... I'm seeing a slightly different error, but I think it's essentially the same problem:
fail: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.
almost sounds like a network issue, but my connection looks pretty stable
I downgraded back to 0.69 and everything worked, went back to 1.0.2 and started getting these errors, so I downgraded a 2nd time to 0.69 and everything is working fine 🤷 ... for now I will stay on 0.69