Skip to content

Conversation

cheatfate
Copy link
Contributor

  • Fix poll block monitor issue when it deadlocks VC.
  • Fix events block monitor issue when it doesn't recover connection when connection has been lost.
  • Add node field to "Block received" log statement.

Fix events block monitor from losing connection forever.
Add node to block received log statement.
@github-actions
Copy link

Unit Test Results

         9 files  ±0    1 071 suites  ±0   35m 25s ⏱️ -15s
  3 699 tests ±0    3 420 ✔️ ±0  279 💤 ±0  0 ±0 
15 763 runs  ±0  15 458 ✔️ ±0  305 💤 ±0  0 ±0 

Results for commit a01a715. ± Comparison against base commit d670af5.

@@ -503,15 +503,15 @@ proc runBlockEventMonitor(service: BlockServiceRef,

while true:
while node.status notin statuses:
await vc.waitNodes(nil, statuses, roles, false)
await vc.waitNodes(nil, statuses, roles, true)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't this be waiting for the specific node to become connected?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

waitNodes using event which indicates that some of the changes in nodes status happened, so we wait for node status to be changed, checks status, if status is not in {RestBeaconNodeStatus.Synced} it continues to waiting changes.

@arnetheduck arnetheduck merged commit c534a28 into unstable Jun 28, 2023
@arnetheduck arnetheduck deleted the block-monitor-fixes branch June 28, 2023 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants