Repository navigation
Bind live monitor consumers to exact stream and coverage - #334
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.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.
The monitor health and daily consumers did not supply a trusted live stream and requested checkpoint window to QPK, and profile-wide dashboard/drift lookups could reuse a different stream. Bind the Binance live profile to explicit stream/start/end configuration, require complete requested coverage and at least 10 real returns, and use the same verified snapshot for both consumers. Unrelated research profiles retain their existing paths.
Live drift is computed directly from that verified snapshot and matching profile baseline without reusing unbound prior drift. QPK currently marks interval coverage as not comparable to its generic baseline; the consumers therefore report that live score as unavailable instead of inventing comparability. This does not claim live-data or service adoption.
Validation: exact current admitted QPK source f6f2079f6b53d3cbb3b72bdcc5c2476ed8f170f1, Python 3.12, complete affected monitor test file: 70 passed and 50 subtests; compile checks and git diff --check passed. Includes synthetic actual QPK collection and cross-stream snapshot/drift regressions. No real data, AI call, send, configuration or service switch.