feat: persistent per-provider key counters#32
Merged
Conversation
Preview torn downThis PR's ephemeral environment was cleaned up.
Reopen the PR if you need to spin it back up. |
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
Per-provider counters live in a new
countersbucket insidecache.db, updated transactionally with everySet/Delete.Counter keys are derived from the cache key prefix via a small
prefixOfclassifier:ttml,kugou,qq,legacy,negative,unknown./statsnow reads live counts viapersistentCache.Counts()in microseconds. New response fields:keys_total,keys_by_provider,last_reconciled_at,last_duration_ms,status(seeding|ready|error), andlast_erroron failure.StatsCachewas reshaped into a small lifecycle struct. The 24h scan is gone. A weekly backgroundReconcileCounterscorrects drift from rare type-flips (e.g. permanent no-lyrics sentinels stored under provider prefixes).Clear()wipes the counters bucket in the same transaction as the cache wipe. Restore handler triggers a reconcile so its response reflects the restored DB.