Running Vercel community PHP on a side proejct and this bug has started appearing out of nowhere. suggesting Vercel changed something as of last night:
The same code that ran and deployed yesterday is failing today due to the /opt/wrapper issue
Vercel Staff
Hi , welcome to the Vercel Community!
Sorry that you are facing this issue.
Could you share your public repo or a minimal reproducible example. That will let us all work together from the same code to figure out what’s going wrong.
The strange thing is, it works on certain accounts (as you can see from the github issue).
I’m having the same issue for a Go project deployed to Vercel.
The same deployment that worked a few days ago can no longer be redeployed successfully.
After redeploying, I get the following panic:
panic: no such file or directory
goroutine 1 [running]:
main.checkForLambdaWrapper()
./main__vc__go__.go:24 +0x14a
main.main()
./main__vc__go__.go:29 +0x13
So I checked the vercel code, and it looks like Vercel is injecting the AWS_LAMBDA_EXEC_WRAPPER environment variable into the Lambda runtime. My app tries to execute whatever path is provided by this variable, but it points to a file that does not exist in the execution environment, which causes the panic.
would very much appreciate if this were fixed before the weekend.
fyi if this broke functionality on one of your projects, instead of redeploying an old stable version (which will introduce the bug), just promote that old version to your environment, which fixed for me. (but of course now can’t release anything new.)
Vercel Staff
Hi everyone, thanks for providing the inputs. Let me escalate this internally to get more information for you.
Vercel Staff
, the Go issue was resolved yesterday. Can you confirm if you are still facing that issue?