Hi there, I’ve been seeing 499 errors on my deployment script throughout the day. I can see on Fly Status that there are reported intermittent cases for this, but in my case I can’t get an urgent deployment out.
The relevant logs:
#13 pushing layer sha256:927412abf89d6e6aedc9414f179e81c94bf7338073dceaaca2415bdc633057af 12.0s done #13 ERROR: failed to push registry.fly.io/… failed to copy: unexpected status from PUT request to http://_api.internal:5000/v2/…?digest=sha256%3A927412abf89d6e6aedc9414f179e81c94bf7338073dceaaca2415bdc633057af&ns=registry.fly.io: 499 status code 499
@hstro We’ve shipped a change that should fix this. Could you give it another shot?
If you hit the 499 again, running the deploy with fly deploy --depot=false should also allow you to get the deploy out, as it seems to be isolated to the push from the depot builders only
@Sam-Fly I’ve been trying to get builds out all day and I’m running into the same error. I’m currently trying --depot=false, but if I’m reading you messages right, I think that suggest the fix you released didn’t work (at least, not for my scenario).
I believe the scenario you happened upon is that app names with consecutive dashes or underscores (e.g., test--app) will not work through the registry changes now applied to Depot builders. We didn’t manage to get a fix for that particular edge-case in today but it will be rolled out sometime tomorrow. Until then, --depot=false (or adjusting your app name if possible) is the suggested workaround.
Apologies for the inconvenience getting these changes rolled out caused for you and your builds today.
ah, gotcha. yea, changing that would be challenging. it’s unfortunately a key part of a bunch of my tooling. thanks for the update, I’ll use –depot=false for now.
