fix: restored dormant window priming - #200
Merged
Merged
Conversation
- Allowed newer dormant epochs after verified quota resets. - Preserved duplicate protection across restarts. - Excluded backend-gated reserve quota from proactive priming.
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
1 participant
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.
Quota resets can reopen dormant weekly windows before the previous verified reset date. The primer now permits a confirmed newer dormant epoch while preserving duplicate protection for admitted and unresolved requests, including after restart.
gpt-reservepool from proactive priming; ordinary windows remain eligible and unknown pools still report resolution errors.Validation:
go test -race -count=1 ./...,go build ./...andgo vet ./...passed. Independent code review found no actionable issues. Live upstream routing, continuity, latency and degraded rescue passed on the merged commit and packaged executable. Deployedv0.32.8locally; installed binary hash matched the tested package. Fresh weekly reset timestamps remained fixed, primer error cleared, and production probes returned HTTP200and WebSocket101with zero errors.