We use circle ci and vercel cli to build and deploy changes to our website, it stopped working today and started showing the following error on the console.
Running this command
vercel deploy --scope xxxxxxxx --prebuilt --archive=tgz --token=${VERCEL_TOKEN}
Vercel CLI 37.5.2
Deploying xxxxxxxx
Exited with code exit status 1
We run multiple releases a day and this is currently making that impossible with circle ci, I can see the deployment as cancelled on the vercel dashboard
swarnava
September 20, 2024, 2:51am
2
This is likely due to huge cache or similar. Are you able to deploy without cache? What is the file size are you deploying? For example, if you are using yarn, you can run yarn cache clean before deployment
Thanks @swarnava any idea what the limit is, the main issue is trying to do this on the pipeline and not seeing any feedback other than this error, I have tried clearing the node modules cache with npm cache clear --force but the error still remains
swarnava
September 20, 2024, 1:03pm
4
How much file size are you uploading? I have seen often uploading 500-600 mb worked always
@swarnava Testing on local it looks like we have 4+gb, the website has more than 20k pages and we use ssg for about 8k of those pages
swarnava
September 20, 2024, 4:42pm
6
Can you run --debug parameter and share us the output of the upload size when you run vercel deploy?
@swarnava here’s the result, it’s about 800mb
Vercel CLI 37.5.3
[debug] [2024-09-20T17:21:34.983Z] user supplied known subcommand: “deploy”#1 → GET https://api.vercel.com/v2/user #1 ← 200 OK: sfo1::tcqc6-1726852895198-de3bd5aeedbe [288ms]#2 → GET https://api.vercel.com/v1/teams #2 ← 200 OK: sfo1::tcqc6-1726852895312-c5cab17b2eaa [83ms]#3 → GET https://api.vercel.com/teams/*****************************?teamId= *****************************#4 → GET https://api.vercel.com/v9/projects/********************************?teamId= *****************************#3 ← 200 OK: sfo1::tcqc6-1726852895435-ad42db7eb1fc [81ms]#4 ← 200 OK: sfo1::fgcsz-1726852895556-258672825a76 [278ms]https://api.vercel.com https://api.vercel.com/v2/files?teamId= *****************************https://api.vercel.com/v2/files?teamId= *****************************
swarnava
September 23, 2024, 4:58am
8
Thanks! It appears due to Function / Lambda size which is likely increased in your recent builds. Have you tried removing some dependencies or optimise to see if it helps?
swarnava
September 24, 2024, 5:27am
9
Could you please perform a new deployment to test whether the Request Entity too Large issue has been resolved?
We rolled out a fix earlier today and so far our internal testing has been successful.
Yes it works now, thank you @swarnava
system
September 26, 2024, 11:07am
11
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.