Skip to content
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

🐛 BUG: Wrangler retries deployments on 4xx errors? #7714

Closed
irvinebroque opened this issue Jan 9, 2025 · 1 comment · Fixed by #7831
Closed

🐛 BUG: Wrangler retries deployments on 4xx errors? #7714

irvinebroque opened this issue Jan 9, 2025 · 1 comment · Fixed by #7831
Labels
bug Something that isn't working

Comments

@irvinebroque
Copy link
Contributor

Which Cloudflare product(s) does this pertain to?

Wrangler

What versions are you using?

3.101.0

What operating system and version are you using?

mac latest

Please provide a link to a minimal reproduction

https://github.com/irvinebroque/test-provisioning

Describe the Bug

If I try to deploy a Worker like https://github.com/irvinebroque/test-provisioning that eventually results in an 4xx error like this:

-- START CF API RESPONSE: Bad Request 400
✘ [ERROR] A request to the Cloudflare API (/accounts/ID/workers/scripts/test-provisioning) failed.

  workers.api.error.bucket_not_found [code: 10085]

When I set WRANGLER_LOG="debug" to view what API requests happen under the hood, I see what looks to me like Wrangler retrying deployments?

-- START CF API REQUEST: PUT https://api.cloudflare.com/client/v4/accounts/ID/workers/scripts/test-provisioning?excludeScript=true
-- END CF API REQUEST

-- START CF API RESPONSE: Bad Request 400
-- END CF API RESPONSE
-- START CF API REQUEST: PUT https://api.cloudflare.com/client/v4/accounts/ID/workers/scripts/test-provisioning?excludeScript=true
-- END CF API REQUEST

-- START CF API RESPONSE: Bad Request 400
-- END CF API RESPONSE

-- START CF API REQUEST: PUT https://api.cloudflare.com/client/v4/accounts/ID/workers/scripts/test-provisioning?excludeScript=true
-- END CF API REQUEST

-- START CF API RESPONSE: Bad Request 400
-- END CF API RESPONSE

Is this necessary? Are these retries? If so, why retry on 4xx?

Please provide any relevant error logs

No response

@irvinebroque irvinebroque added the bug Something that isn't working label Jan 9, 2025
@github-project-automation github-project-automation bot moved this to Untriaged in workers-sdk Jan 9, 2025
@penalosa penalosa moved this from Untriaged to Backlog in workers-sdk Jan 13, 2025
@penalosa penalosa mentioned this issue Jan 20, 2025
9 tasks
@github-project-automation github-project-automation bot moved this from Backlog to Done in workers-sdk Jan 20, 2025
@irvinebroque
Copy link
Contributor Author

Thanks @penalosa

@nevikashah @korinne probably changes metrics for frequency at which we see these errors returned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant