-
Notifications
You must be signed in to change notification settings - Fork 251
fix(node): race on caught up #3133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+7
−1
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 3017
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 869
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 6599
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 874
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 1013
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 2363
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 3638
Pipeline can complete catchup before pending cache events are processed.
PendingCount()only measures channel buffer length (line 471-472) and misses two important pipeline states:Pending cache events: When
processHeightEvent()encounters an out-of-sequence block, it stores it in cache viaSetPendingEvent()(line 599). ThependingWorkerLoop()polls this cache every 10ms (line 481) and re-queues events toheightInChwhen the sequence is complete (line 1109-1111). These cache events don't appear inPendingCount().In-flight processing: Events dequeued from
heightInCh(line 354) remain in-flight duringprocessHeightEvent()execution, which performs I/O and state validation (lines 584-602). This work isn't tracked by channel depth.The evidence:
Stop()callswg.Wait()(line 216) to wait for all worker goroutines, then after goroutine completion, drainsheightInChin a loop (lines 221-237). This pattern shows the channel can be empty while the pipeline hasn't reached true quiescence.Line 318 in failover.go declares catchup complete as soon as
PendingCount() == 0, which creates a race where pending cache events or in-flight processing aren't accounted for.Implement a dedicated idle signal in Syncer that waits for all three stages: empty channel, no in-flight processing, and empty pending cache.
🤖 Prompt for AI Agents