sync: fix range recovery test vector - #1038
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
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.
Fixes the macOS
test (macos-latest)CI failure from https://github.com/blockblaz/zeam/actions/runs/29247771524/job/86810099947.Summary
forkMismatchRecoveryStart re-anchors to a recent justified ancestortest vector that failed in the macOS unit-test jobblocks_by_rangeserving window, so the helper correctly returned nullValidation
zig fmt --check pkgs/node/src/blocks_by_range_sync.ziggit diff --checkzig build test --summary allstill fails in this runner becauserustupis not installed, but the macOS failure signature from the linked job (expected 9340, found null) is gone from the local log.