Fix backup rehearsal startup and completed coordination wording - #7
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
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.
The backup rehearsal started the Nucleus image with TLS enabled, while its loopback client used plain pgwire. Start the proof engine with explicit data mount, transport and memory settings. The corrected rehearsal restored the production copy and found all five waiting decisions with compatible fingerprints; full ordered-history verification is recorded separately.
A real standalone API/client coordination also reached completion through both merge approvals and its compatibility scan, but its client description still claimed the check was owed. Point that description to the actual result below.
Validation: production snapshot checksum verified, corrected isolated restore/preflight passed, and the independent HTTP API/client pair test passed at both exact merged commits. All CI jobs and local lint, 1,412 runtime tests, 102 script tests (one existing skip), 136 web tests and the web build pass. The isolated restore also matched all 352 runs, 18,537 events and the exact ordered-history digest. No production Ship rollout yet. Original failed rehearsal and coordination receipts are retained.