Skip to content

Handle missing five-hour quota windows#1

Merged
LUOYEcode merged 3 commits into
mainfrom
agent/handle-missing-five-hour-quota
Jul 13, 2026
Merged

Handle missing five-hour quota windows#1
LUOYEcode merged 3 commits into
mainfrom
agent/handle-missing-five-hour-quota

Conversation

@LUOYEcode

Copy link
Copy Markdown
Owner

Summary

  • Identify five-hour and weekly quota windows by windowDurationMins instead of assuming fixed primary/secondary positions.
  • Keep the positional mapping as a fallback for older app-server responses without duration metadata.
  • Leave the five-hour percentage and reset text blank when that window is not provided, while continuing to show the weekly quota.

Why

Codex can temporarily return only a 10,080-minute weekly window and place it in primary, with secondary set 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.ps1 succeeds on Windows.
  • Parser checks pass for weekly-only, reversed-position, and legacy duration-less responses.
  • Live app-server response verified with primary.windowDurationMins = 10080 and secondary = null.
  • Running UI verified with an empty 5h value and a populated 7d value.
  • No tokens, logs, binaries, or personal paths are included in the commits.

@LUOYEcode LUOYEcode marked this pull request as ready for review July 13, 2026 05:57
@LUOYEcode LUOYEcode merged commit 955f40f into main Jul 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant