Feature set 127. - #54
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Makes the generator say what stopped it, and stop when stopping is the right answer.
On 2026-08-03 a 400-image batch ran for the full six-hour job ceiling, attempted ~70 candidates
and generated none, logging
gave up after repeated rate limitingevery five minutes. It was notrate limited. The account had run out of prepaid credit, which Gemini reports as
429 RESOURCE_EXHAUSTED— the same status as throttling — with this body:Only a per-day quota ended a run, so this read as a burst limit and was retried forever. The 429
body was parsed to classify it and then discarded, never logged, so nothing in six hours of output
said what was actually wrong. The first accurate signal was a billing page showing no spend.
What changed
ClassifyRefusalsorts a 429 intoBurst,DailyQuotaorCreditsExhausted. Creditexhaustion is matched first because it is the only one carrying no
detailsarray, so checkingit after the quota tests would fall through them.
GenerationHaltedExceptioncarrying the kind, a reason and the detail.
DailyQuotaSpentExceptionis folded into it.no clock will bring is as useless as topping up a healthy account.
free to change, and the next unnamed refusal should cost minutes to diagnose rather than hours.
gave up after N refusals — last was: <detail>replaces the old line, which asserted "ratelimiting" about refusals it had never inspected.
Six tests cover the new classifier against a verbatim capture of the depleted-credit body, the
per-minute limit it must not be confused with, and unreadable bodies, which stay retryable.
Release notes
instead of retrying for hours, and reports the cause, the elapsed time and the fix.