Repository navigation
Quarantine inconsistent discovery snapshots without blocking analytics - #33
Merged
Merged
Conversation
marcociav-exmergo
marked this pull request as ready for review
November 8, 2026 15:00
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.
What changes
A GitHub referrer snapshot reported more unique visitors than total views, causing this scheduled run to fail during
sync-candidate. Because imports validate historical snapshots, a future corrected capture could not unblock publication.Quarantine the entire affected referrer/path snapshot while retaining its original CSV, checksum, revision, and capture timestamp. Keep the capture as a null selection barrier so MetricFlow cannot resurrect older counts. Status and publication metadata identify the quarantine and offending rows. Exact-date/comparison recipes and affected trend windows report unavailable. Valid endpoints and repositories continue through normal validation; malformed inputs and daily traffic violations still fail.
Validation
e32f6b797c62ac4634a4574adae6510bdb1958cb: import, verified build (verification.ran: true), committed-definition check, previous-baseline adoption, Maintain check/verify, and freshness all passed. Status is ready/fresh and the quarantined-date recipe explicitly returns unavailable.Analytics engineering checklist
Baseline change
Release target:
v1.1.2after passing CI and merge.