Fix owner proof failures during index publication - #40
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.
Live Explorer address requests intermittently returned HTTP 502 after the shared node committed QMDB state but before EdgeIndex published its matching checkpoint. A local probe against master saw 16 failures in 30 address-proof requests.
Read the published checkpoint and prepared intent in one index read transaction, selecting the evidence that matches the held QMDB read guard. The existing certificate, canonical block, owner-root and owner-page checks still run before a proof can be returned. Before the database commit, readers continue to use the old checkpoint. Unmatched roots and corrupted evidence fail closed. Log the underlying error when native owner-proof generation fails.