Repository navigation
make/publish-app: correct the 1010 quota gotcha + drop retry-storm - #3
Merged
Merged
Conversation
Field-tested the script publishing a real 42-component app. The 1010 error is NOT a per-second rate limit (as the first version implied) — it's a WINDOWED write quota. Isolated calls and 20-rapid bursts return 200; big back-to-back runs drain it, and it then needs a ~30-60 min cooldown. The old 5x30s retry-storm made it WORSE by hammering the empty bucket. Now: one short backoff+retry, then abort with clear guidance to wait and re-run (idempotent, resumes where it left off). README + docstring updated with the real lesson.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Field-tested the publisher on a real 42-component Make app. Two fixes from what I learned:
--pauseor looping retries doesn't help.