Repository navigation
Conversation
A unanimous unknown anchor is recorded with the observed height of that flush. A later one burns when the tip is fresh and the observed height is above the mark. Co-authored-by: Cursor <cursoragent@cursor.com>
1 task
|
Found 1 test failure on Blacksmith runners: Failure
|
…nchor Co-authored-by: Cursor <cursoragent@cursor.com>
This branch has not been deployed
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.
![Fix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/fix-with-codesmith-light-3x.png)
Stacked on #108. GitHub retargets this to
mainwhen #108 merges.What
An unknown anchor, in either word order for sprout, sapling, orchard, and ironwood, is
Publish::Anchor. Any otherbad txnsreason staysRejected.A unanimous
Anchoris recorded with the observed height of that flush and put back. A later unanimousAnchorburns when the tip is fresh and the observed height is above that mark. The stored height is the first one recorded. A stale tip, or the same height, puts the entry back under the attempt cap.AnchorbesideRetryable,Rejected, orAlreadyMinedisRetryableand is not recorded. A laterAcceptedorAlreadyKnowndoes not clear a mark. A burn does.An entry with no bundle key uses its payload hash as the mark and the burn key on this path only. A unanimous
RejectedorAlreadyMinedstill burns bundle keys only.The anchor requeue is a separate call from the transport requeue. It does not trip
SELECTIVE HOLD-BACK, and an anchor that expires is logged on its own line.Tests
cargo test --manifest-path zeronym/hub/Cargo.toml --lib: 182 passed, 1 ignored.Anchor. A non-anchorbad txnsreason staysRejected.[Anchor, Rejected],[Anchor, AlreadyMined], and[Anchor, Retryable]areRetryable.Anchorrequeues. Another at the same height requeues. After the observed height rises, on a fresh tip, it burns.TIP_STALE_AFTERrequeues.Rejecteddoes not store that hash.Acceptedand oneAnchorin the same flush does not logSELECTIVE HOLD-BACK.Pending
zeronym/hub/deploy/EXPECTED_SHA256, after fix(zeronym): burn a publish verdict only when every endpoint agrees #108's hash commit.reproduce.shhashesgit archive HEAD.Made with Cursor