You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.
+1, I ran into this when pushing multiple images in parallel to a newly created projects (with rules_docker's container_push). The first request succeeds, but the next 10 or so fail with a 503.
We've (not Google) done this by overriding/extending the ShouldRetry function in the RetryTransport class, which was nicely setup to allow that. Is that useful?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice if the pusher retried on 504s and other similar responses that occur when backends are having issues. For example, today: https://status.cloud.google.com/incident/cloud-dev-tools/18003#18003003
The text was updated successfully, but these errors were encountered: