-
Notifications
You must be signed in to change notification settings - Fork 334
get-npm-wrangler-binary endpoint throwing occasional exceptions #1587
Comments
Downloading release https://workers.cloudflare.com/get-npm-wrangler-binary/1.11.0/x86_64-apple-darwin Error fetching release Request failed with status code 500
|
I don't know if it's helpful to mention that I am also experiencing this error; feel free to delete this comment if it's just noisy/duplicative. But I wanted to say that it might make sense to add a temporary note to the installation guide explaining that the |
This should be resolved as of a few minutes ago, when we deployed a (putative) fix. @robinsloan can you try again? If you're still seeing errors, please re-open this issue and share the error message you see! |
Success! I feel honored to know I might have been the last person in the universe to experience this error. Thanks! |
@ispivey When I try to preview my project using wrangler preview --watch or wrangler preview, I keep getting this message: |
@Swatilekha-Roy can you open a new issue about your problem? The new issue template asks a number of clarifying questions that will help ensure you. get an answer. |
🐛 Bug Report
Environment
Steps to reproduce
Repeatedly call
curl -I -XGET https://workers.cloudflare.com/get-npm-wrangler-binary/1.10.3/x86_64-apple-darwin
in your terminal.What did you expect to see?
200 OK with Wrangler binary every time I call it.
What did you see instead?
Occasional 500s with a generic Cloudflare response saying the Worker has thrown an exception.
owner@facility:/tmp$ curl -I -XGET https://workers.cloudflare.com/get-npm-wrangler-binary/1.10.3/x86_64-apple-darwin HTTP/2 500 date: Thu, 08 Oct 2020 07:34:29 GMT content-type: text/html; charset=UTF-8 x-frame-options: SAMEORIGIN cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 expires: Thu, 01 Jan 1970 00:00:01 GMT cf-ray: 5dee2e010b6f2484-FRA server: cloudflare cf-request-id: 05a8bb14a70000248441a56200000001
The text was updated successfully, but these errors were encountered: