-
-
Notifications
You must be signed in to change notification settings - Fork 311
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
fix: start clock last when initializing validator client #6973
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## unstable #6973 +/- ##
=========================================
Coverage 62.49% 62.49%
=========================================
Files 576 576
Lines 61180 61178 -2
Branches 2131 2134 +3
=========================================
+ Hits 38234 38235 +1
+ Misses 22907 22904 -3
Partials 39 39 |
Performance Report✔️ no performance regression detected 🚀🚀 Significant benchmark improvement detected
Full benchmark results
|
is the problem that we could miss the first slot? |
No, it's just that after |
Oh, right! |
yeah, I have not retested the unhealthy log after moving it in constructor (from init previously) and was kinda blindly trusting that it should work there because the beacon health was there as well but noticed this yesterday when experimenting with my multi node setup. |
🎉 This PR is included in v1.21.0 🎉 |
Motivation
Clock needs to be started as late as possible when initializing validator client to ensure all functions are being scheduled.
lodestar/packages/validator/src/util/clock.ts
Lines 48 to 49 in 27012f9
Description
Start clock last when initializing validator client