Skip to content
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

VC: Fix issue when optimistically synced node could block sync committee service functions. #4878

Merged
merged 2 commits into from
May 2, 2023

Conversation

cheatfate
Copy link
Contributor

Issue was reported in discord chat and it affects scenario when multiple BN get used and some of them are optimistically synced.

@github-actions
Copy link

Unit Test Results

         9 files  ±0    1 071 suites  ±0   31m 38s ⏱️ - 1m 16s
  3 670 tests ±0    3 391 ✔️ ±0  279 💤 ±0  0 ±0 
15 653 runs  ±0  15 348 ✔️ ±0  305 💤 ±0  0 ±0 

Results for commit 0268869. ± Comparison against base commit 5ccb085.

@@ -360,8 +360,7 @@ proc publishSyncMessagesAndContributions(service: SyncCommitteeServiceRef,
res.data.root
else:
if res.execution_optimistic.get():
notice "Execution client not in sync; skipping validator duties " &
"for now", slot = slot
notice "Execution client not in sync", slot = slot
Copy link
Member

Choose a reason for hiding this comment

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

per changes to getHeadBlockRoot we can no longer end up in this branch of the logic?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yup

@zah zah merged commit 0c75f9c into unstable May 2, 2023
@zah zah deleted the fix-optimistic-isgood branch May 2, 2023 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants