Handle missing five-hour quota windows#1
Merged
Conversation
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.
Summary
windowDurationMinsinstead of assuming fixed primary/secondary positions.Why
Codex can temporarily return only a 10,080-minute weekly window and place it in
primary, withsecondaryset to null. The previous positional mapping mislabeled that weekly value as the five-hour quota and left the 7d slot unavailable.User impact
When only the weekly quota is available, the meter now shows an empty 5h value and the correct percentage under 7d. Existing responses that include both windows, and legacy responses without duration metadata, remain supported.
Verification
.\build.ps1succeeds on Windows.primary.windowDurationMins = 10080andsecondary = null.