Skip to content

test: derive the Codex header fixture's reset from the clock - #402

Merged
MagicalTux merged 1 commit into
masterfrom
fix/codex-header-fixture
Sep 15, 2026
Merged

MagicalTux merged 1 commit into
masterfrom
fix/codex-header-fixture

Conversation

@MagicalTux

Copy link
Copy Markdown
Member

The reset epoch in test/codex-quota-headers.test.js was 2026-09-15 06:27 UTC. Once it passed, the weekly window was swept as expired before the assertion read it, so npm test went red on master and on every open PR (each shows the same single failure). The reset is now derived from the clock, as the other quota fixtures already do. A scan of test/ finds no other epoch fixture within the next sixty days.

🤖 Generated with Claude Code

The reset epoch in codex-quota-headers.test.js was 2026-09-15 06:27 UTC. Once
that passed, the weekly window was swept as expired before the assertion read
it, and the suite went red on master and on every open PR.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@MagicalTux
MagicalTux merged commit f2b58b7 into master Sep 15, 2026
5 checks passed
@MagicalTux
MagicalTux deleted the fix/codex-header-fixture branch September 15, 2026 15:40
rikbrown added a commit to rikbrown/teamclaude that referenced this pull request Sep 15, 2026
Rebases the fork onto upstream master 1779db6 (1.1.20 plus KarpelesLab#374-KarpelesLab#403).
No new fork feature of its own: this ships upstream's 13 commits and the
reshaping the rebase required.

Upstream brings a version label in the dashboard header, provider names
on the account rows of a mixed pool, Codex quota fixes across the 5h and
weekly windows, spreading for requests that carry no session id, and
outcome accounting on the same classification path every routing
decision already read.

Two fork commits dissolved into upstream, both merged there today: the
dashboard key prompt (KarpelesLab#381), and the expiring Codex header fixture,
which upstream fixed independently as KarpelesLab#402. The locally-served account
ordering went up as KarpelesLab#376, so only its fork-only documentation remains
here; and the header commit keeps the branding alone, now that upstream
resolves and draws the version itself.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
rikbrown added a commit to rikbrown/teamclaude that referenced this pull request Sep 19, 2026
Rebases the fork onto upstream master 1779db6 (1.1.20 plus KarpelesLab#374-KarpelesLab#403).
No new fork feature of its own: this ships upstream's 13 commits and the
reshaping the rebase required.

Upstream brings a version label in the dashboard header, provider names
on the account rows of a mixed pool, Codex quota fixes across the 5h and
weekly windows, spreading for requests that carry no session id, and
outcome accounting on the same classification path every routing
decision already read.

Two fork commits dissolved into upstream, both merged there today: the
dashboard key prompt (KarpelesLab#381), and the expiring Codex header fixture,
which upstream fixed independently as KarpelesLab#402. The locally-served account
ordering went up as KarpelesLab#376, so only its fork-only documentation remains
here; and the header commit keeps the branding alone, now that upstream
resolves and draws the version itself.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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