Keep telemetry retries inside the original consent period - #2862
Draft
Chris0Jeky wants to merge 1 commit into
Draft
Keep telemetry retries inside the original consent period#2862Chris0Jeky wants to merge 1 commit into
Chris0Jeky wants to merge 1 commit into
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
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.
Fixes a concrete race: an in-flight upload failure could requeue events after consent was withdrawn. A consent epoch now prevents that, including withdrawal followed by a fresh opt-in. Revocation clears the queue and timer before storage writes; blocked storage no longer skips cleanup.
Adds five Vitest regressions and a local-first Observatory integration boundary. No public SDK, collector URL, CSP relaxation, server enablement or v0.3 policy change.
Portfolio system: Chris0Jeky/Pulseboard#15. Host tests have not been executed here; draft pending the targeted telemetry tests and existing frontend checks. This does not claim to recall data already sent or to enable v0.4 analytics.