Repository navigation
The server rebuilds the cache: confirmed, not inferred - #17
Merged
Merged
Conversation
#16 said data_cache/ and cot_data.db are pushed by nothing and that the server regenerates the cache, with an explicit hedge that this was inference from the old push having been broken since PR #12 rather than something anyone had confirmed. Confirmed by the maintainer 2026-08-04. The hedge is removed and the mechanism stated: CotIndexer writes per-instrument parquet under COTMETRICS_CACHE on first use and busts it on the upstream cotdata.schema_version() plus METRICS_CACHE_VERSION, so a store push is the only input it needs. The consequence worth knowing is a latency one rather than a missing payload: the first request after a release runs against a cold cache. That closes the last open question from the deprecation. Nothing is pushed by nothing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Follow-up to #16, which said
data_cache/andcot_data.dbare pushed by nothing and that the server regenerates the cache — with an explicit hedge that this was inference from the old push having been broken since PR #12, rather than something anyone had confirmed.Confirmed by the maintainer, 2026-08-04. The hedge comes out and the mechanism goes in:
CotIndexerwrites per-instrument parquet underCOTMETRICS_CACHEon first use and busts it on the upstreamcotdata.schema_version()plusMETRICS_CACHE_VERSION, so a store push is the only input it needs.The consequence worth knowing is a latency one rather than a missing payload: the first request after a release runs against a cold cache. That is one slow request, not an absent artifact.
This closes the last open question from the deprecation. Nothing is pushed by nothing.
Testing
170 passed.ruffclean.bash -nclean, script still exits 2.🤖 Generated with Claude Code