Fix cross-session chain break attribution - #48
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.
A modified record in one session could inherit coverage from a later signature when the shared collector stream crossed into another session. The earlier session was then reported as
verified_completeeven though the next record exposed a broken chain.This change attributes an ambiguous broken boundary to both adjacent sessions and records it once per session. Both sessions become inadmissible, and
sequence_verifiedrejects the altered position. It adds an end-to-end regression for the sparse signed, multiplexed-stream case and refreshes generated repository counts.Validation: