Skip to content

fix(quota-history): keep Mistral accounts grouped after restart - #14

Merged
rune-gh merged 1 commit into
mainfrom
fix/mistral-quota-restart
Nov 22, 2026
Merged

rune-gh merged 1 commit into
mainfrom
fix/mistral-quota-restart

Conversation

@rune-gh

@rune-gh rune-gh commented Nov 22, 2026

Copy link
Copy Markdown
Owner

The quota panel can count an API key and a Vibe key for the same Mistral customer as two budgets immediately after a restart.

Persist verified customer fingerprints in the quota database and restore them before serving history. Carry known fingerprints to a newly configured database and save a verified identity even if shutdown cancels the usage sample. Existing databases learn their fingerprints on the first successful identity poll after upgrading.

Proof includes the restart regression, 30 race-detector runs, a compiled local server that returned one account before its first poll, and make verify.

Reviewed with sol-loop: 4 rounds with GPT 6.2 Sol on high. Sol verdict: approved

Created with GPT 6.2 Sol in Codex.

@rune-gh
rune-gh merged commit 7f7967d into main Nov 22, 2026
6 checks 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