-
Notifications
You must be signed in to change notification settings - Fork 299
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
Just not working need help #355
Comments
Hi @Metastem. Can you please upgrade it to latest version? [email protected]? |
I'm facing this issue
|
Hi @gamerhost31. You should use latest version |
I'm seeing this same error with 0.5.2 specifically when letting it deploy automatically from GitHub. When deploying with It also seems to be repeating Creating lambda, Downloading user files, Downloading PHP runtime files, Installing Composer dependencies several times before failing. Build log
Failing source code: https://github.com/DenverCoder1/github-readme-streak-stats/tree/vercel |
Hi guys! I'm seeing this same error when deploying with This is my
and this is the log
|
Hi @amorimleonardo, @DenverCoder1!, Navigate to your Project Settings, uncheck the following, save it and redeploy your project. |
I tried to do this, but..... still not working for me. I tried change Node.js to test others configurations but nothing |
Deploying through the site is working for me now after changing that setting. |
I am also facing the exact same issue as @amorimleonardo . I have unchecked the box as well using the latest version of Node.js as 18.x but while creating build from auto deploy from github it is giving the error of
|
Hi folks. I've reached Vercel's Runtime Team, to help identify the problem. Stay tuned. |
To follow up, is anyone still seeing failed builds on Vercel with the error: |
Hi folks. Are you still facing this error? |
It's working again in my side, thanks anyway. |
I have the same problem.here is my build log
I've tried all solutions,but none of them works. |
Hello there, Yep still the same issue today & yesterday with 0.5.2 (no include source & nodejs 16) : "Error: EISDIR: illegal operation on a directory, read" Is the issue on Vercel side ? |
It looks like it's issue on Vercel side. I was trying Discord, but no luck. I've started a discussion vercel/vercel#9239. We will see. |
I'm facing the same issue on my projects. |
I am not facing that issue anymore. |
Question
Cloning completed: 646.02ms
07:32:59.866 | Running "vercel build"
07:33:00.377 | Vercel CLI 28.6.0
07:33:00.557 | > Installing Builder: [email protected]
07:33:05.109 | 🐘 Downloading user files
07:33:05.109 | 🐘 Downloading PHP runtime files
07:33:05.213 | 🐘 Creating lambda
07:33:13.470 | Error: The Runtime "[email protected]" is using "nodejs12.x", which is discontinued. Please upgrade your Runtime to a more recent version or consult the author for more details.
07:33:13.471 | Learn More: https://github.com/vercel/vercel/blob/main/DEVELOPING_A_RUNTIME.md#lambdaruntime
The text was updated successfully, but these errors were encountered: