Repository navigation
Prepare bounded analytics sessions with incremental updates - #28
Merged
Merged
Conversation
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.
Large event histories currently require rebuilding playback sessions for each analytics request. This change prepares bounded, immutable session generations and compact report summaries, then publishes complete generations atomically for dashboard/API readers. New and late events rebuild affected sessions; retired generations are reclaimed after a reader grace period.
The reader and processor are independently configurable and default off; both can be scoped to selected spaces for a bounded rollout. Migrations are additive; historical preparation remains an explicit operation. Raw events remain authoritative. Includes portable operation documentation and reusable range-report interfaces for additional analytics features.
Also requires plug_crypto >= 2.2.1, updates the lockfile, and covers malformed playback tokens with regressions.
Validation: complete local Core and SaaS suites, focused session/publication/cleanup tests, and concurrent ingestion/read/recovery testing. Hosted activation remains a separate staged rollout.
CI setup uses the public Ubuntu package mirror and omits unrelated recommended packages after a hosted-runner mirror timeout prevented the sandbox tests from starting.