-
-
Notifications
You must be signed in to change notification settings - Fork 306
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: check pubkey or validator index known to a state #7284
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## unstable #7284 +/- ##
============================================
- Coverage 48.91% 48.90% -0.02%
============================================
Files 601 601
Lines 40182 40194 +12
Branches 2061 2060 -1
============================================
+ Hits 19655 19656 +1
- Misses 20489 20500 +11
Partials 38 38 |
Performance Report✔️ no performance regression detected Full benchmark results
|
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.
LGTM
This will be hard to reproduce, isn't the only way to trigger this issue if we run the epoch transition twice, ie. if there is a reorg across epoch boundaries? From looking at mekong nodes, there is just a single node (lodestar-geth-3) that has this issue. |
Motivation
Got this error in mekong devnet found by @nflaig
Description
Consider this scenario when we have multiple epoch transitions per epoch, given n is the epoch transition slot
pending deposits of the whole epoch are processed by pulling up (n-1) state, then we add pubkeys to
indes2pubkey
then at slot n, we process epoch transition again, found validator index from
index2pubkey
but validator is not added to registry of the state, then the issue happenTo resolve it, I added
isPubkeyKnown()
function andisValidatorKnown
utils and use them at concerned place.Steps to test or reproduce
resync mekong?