Prefer absolute reset_at epoch over relative reset_after_seconds for Codex#700
Merged
Conversation
…Codex The Codex wham/usage API returns reset_at (absolute Unix epoch) alongside reset_after_seconds (relative). The relative value drifts by network round-trip latency (~18s observed). Now prefer the absolute timestamp, falling back to reset_after_seconds when absent. Applied to all four windows: primary (5h burst), secondary (weekly), and both Spark windows.
The semgrep-action@v1 Docker image (returntocorp/semgrep-agent:v1) is too old to handle severity=MEDIUM from current registry rules, causing every run to crash with ValueError. Install semgrep via pip instead so the latest version is always used.
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
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
3 participants
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.
Changes
The Codex wham/usage API returns
eset_at (absolute Unix epoch) alongside
eset_after_seconds (relative). The relative value drifts by network round-trip latency (~18s observed in live testing). This PR prefers the absolute timestamp, falling back to
eset_after_seconds when
eset_at is absent.
Scope
eset_at is missing
Verification