-
Notifications
You must be signed in to change notification settings - Fork 749
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: Possible race condition or failure with static assets upload with wrangler deploy
#7555
Comments
More details
|
wrangler deploy
static assets upload
wrangler deploy
static assets uploadwrangler deploy
I don't think this is a race condition. The way that asset uploads work is that they need at least one deployed worker to attach the assets to. So on a brand new Worker we create a placeholder.
Can you check that your Worker is actually valid? Did you forget to provide a default export containing a |
Which Cloudflare product(s) does this pertain to?
Wrangler, Cloudflare workers with Static Assets enabled.
What version(s) of the tool(s) are you using?
3.95.0 [Wrangler]
What version of Node are you using?
20.18.1
What operating system and version are you using?
Ubuntu 22.04.5 LTS
Describe the Bug
Observed behavior
Our CI deploys have all of a sudden been failing non-deterministically. We deploy from Github CI using a custom script that shells out to
npx wrangler deploy
and it will take anywhere from 2 to 20 retries before the deploy passes. We have observed this happening since Dec 12 4:32 ET.UPDATE: It seems like a possible race condition or failure related to the static assets upload. The worker gets created, and upon inspection in the Cloudflare Workers UI, I see a single
worker.js
file with contents:The deploy error:
Expected behavior
Deploys work deterministically.
Steps to reproduce
Stripped down wrangler.toml:
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response
The text was updated successfully, but these errors were encountered: