fix(ws): pin near-tip getBlock to EvmLeaderUpstream - #14
Merged
shpookas merged 3 commits intoJul 31, 2026
Conversation
Direct tip/tip+1 getBlock reads set UseUpstream to the primary leader (typically the WS ingress advanced by SuggestLatestBlock) on first forward — same idea as PR11 tip re-fetch pin, so the lagging sibling is not tried first. Co-authored-by: Cursor <cursoragent@cursor.com>
4 tasks
xray — see through AI slop with deterministic architecture PR diff reviews |
Drop helper + dedicated HTTP test; keep only the small UseUpstream pin next to partitionUpstreamsByLatestBlock. Co-authored-by: Cursor <cursoragent@cursor.com>
Flatten nested Forward pin into early-return helper; assert lagging sibling gets zero hits on concrete tip getBlock. Co-authored-by: Cursor <cursoragent@cursor.com>
jleeh
approved these changes
Jul 31, 2026
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
2 participants
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
Network.Forward, afterpartitionUpstreamsByLatestBlock, pin near-tipeth_getBlockByNumber(bnin[leader, leader+1]) toEvmLeaderUpstreamviaUseUpstreamwhen unset.Notes
networks.goonly. No escape-hatch / SkipFallbackEscape changes.Test plan
TestHttpServer_GetBlockByNumberLatest_RefetchPinsEvmLeaderUpstreamstill passes