This repository has been archived by the owner on Dec 20, 2024. It is now read-only.
An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help #6559
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
Using v3.9 of python and suddenly starting to get this error.
I have no idea why its falling over as the logs on Vercel isn't giving me enough information to try fix it.
It runs locally fine and recently moved to pipenv as seems that might be better for vercel python function.
Any ideas would be greated appreciated.
Example
No response
Steps to Reproduce
Any change on my repo , causes Vercel to rebuild deployment of my project.
[14:18:55.425] Running build in Washington, D.C., USA (East) – iad1
[14:18:55.662] Cloning github.com/buildwithdan/flask-portfolio (Branch: simple, Commit: 3bf3cf4)
[14:18:56.038] Previous build cache not available
[14:18:56.070] Cloning completed: 407.447ms
[14:18:56.070] Running "git diff --quiet HEAD^ HEAD ./ ':(exclude)README.md'"
[14:18:57.013] Running "vercel build"
[14:18:57.998] Vercel CLI 33.7.1
[14:18:59.708] Installing required dependencies...
[14:19:06.478] Build Completed in /vercel/output [7s]
[14:19:06.612] Deploying outputs...
[14:19:09.416] An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help
[14:19:11.540]
Beta Was this translation helpful? Give feedback.
All reactions