Add shard-0 clean database recovery producer - #5104
Open
polymorpher wants to merge 9 commits into
Open
Conversation
Introduce the strict read-only LevelDB opener, fail-closed write guards, recovery anchors, key classification, and hashed report helpers used by every producer stage. Co-authored-by: Cursor <cursoragent@cursor.com>
Compare two baseline copies for agreement and export a checksummed block and certificate bundle from a donor database. Co-authored-by: Cursor <cursoragent@cursor.com>
Replay the exported bundle into a working copy up to the pinned target, then compact the result for the sealed payload. Co-authored-by: Cursor <cursoragent@cursor.com>
Walk state, certificates, and logical digests, then seal a checksummed release directory with an install template. Co-authored-by: Cursor <cursoragent@cursor.com>
Cover crash, fault, and localnet producer paths and document the package test map. Co-authored-by: Cursor <cursoragent@cursor.com>
Wire inspect, inventory, export, replay, compact, verify, compare, and package subcommands with stable exit codes. Co-authored-by: Cursor <cursoragent@cursor.com>
Provide operator wrappers for each pipeline stage plus fixture generation for the clean-DB producer. Co-authored-by: Cursor <cursoragent@cursor.com>
Add the test-recovery target, install lsof for offline isolation checks, and register the producer binary. Co-authored-by: Cursor <cursoragent@cursor.com>
Add the operator guide for the Aug 8 snapshot plus forensic donor, the CLI contract, and the pinned 92730034 target notes. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
harmony-recovery-dbpipeline for inspecting an Aug 8 shard-0 snapshot, exporting a verified forensic bundle, and replaying to the pinned recovery targetTest plan
make test-recoverybash scripts/recovery/e2e-localnet.shgo vet ./internal/recoverydb/... ./cmd/harmony-recovery-db/go build ./...Made with Cursor