-
Notifications
You must be signed in to change notification settings - Fork 9
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
Vercel timeout #95
Comments
Are you sure this issue is related to the number of retries? How long does your Vercel deployment take? |
It takes about 20minutes, we're statically building a ton of pages. Just checked the code and it seems like everything happens in a while loop
Is there any chance we can add a timeout between requests? Seems like this is just hammering vercel api without any delay. I think 5secs would be nice, ideally configurable |
@cipriancaba I believe #97 might solve your issue. (PR from first time contributor) |
Merged through #98 Could you let me know if this change improves your issues? |
This other PR should help as well. I'm closing this, let me know if anything doesn't work as expected. |
Works great, much appreciated @Vadorequest |
I haven't done much! @namoscato @dlively1 are to thank for those :) |
Describe the bug
We have some longer deploy times and use this to correctly enforce the result status of the vercel deployment, but after enabling debug mode, we noticed that after a while, the vercel request will timeout
FetchError: request to https://api.vercel.com/v11/now/deployments/get?url=********.vercel.app failed, reason: connect ETIMEDOUT 76.76.21.112:443
I think this is a ddos protection on vercel's side
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It would be really helpful if we could configure the retry step (eg: as opposed to checking status every 5 seconds, we can do it every 30 seconds)
Much appreciated
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: