Repository navigation
fix(graph-db): fingerprint drifting corruption verdicts - #4735
Closed
ScriptedAlchemy wants to merge 1 commit into
Closed
ScriptedAlchemy wants to merge 1 commit into
ScriptedAlchemy wants to merge 1 commit into
Conversation
|
This was referenced Nov 3, 2026
Owner
Author
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.
Root cause
Refs #4571. The terminal drifting-fault event introduced by #4574 already names the store and prints both raw fault messages, but it does not carry stable fingerprints for the first and second verdicts. Operators comparing repeated corruption incidents must treat potentially lengthy raw messages as identifiers.
Focused change
first_fault_fingerprintandsecond_fault_fingerprintas SHA-256 digests to the existing ERROR-levelstore_corrupt_not_deterministicevent, reusing the same SHA-256 authority as the deterministic-deletion event.Corruptrefusal and no-deletion behavior. No locks, recovery thresholds, store layout, permissions or admission controls change.Evidence and validation
Verified the published commit against current
master: one changed file, 10 added lines, zero deletions. Reviewed the single event site and regression assertions. Rust compilation, rustfmt and the regression have not run locally because the available environment lacks the mandated Bazel/Rust toolchain; hosted CI must execute the owning Rust tests on this exact head. No runtime improvement is claimed.Remaining scope
This completes only the event-fingerprint portion of #4571. Operator-visible retained corruption in Doctor/status is addressed by separate unmerged #4700 and needs its own CI and default-branch validation. Keep #4571 open.