fix: derive quota windows from duration#74
Merged
Conversation
- Used provider-reported periods for shared and scoped quota windows. - Added canonical duration keys and generic period calculations. - Reset stale burn history after unobserved window periods.
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.
What changed
Why
OpenAI temporarily suspended five-hour windows and returned weekly limits through
primary_window. Positional parsing labelled those weekly limits as five-hour windows, corrupting pace and aggregate calculations.Impact
Current weekly-only Codex responses render as
7d, while normal five-hour plus weekly responses remain compatible. JSON and cache schemas remain unchanged.Validation
go test -race -count=1 ./...go vet ./...go build ./...limit_window_secondsagainstcq check codex --json