-
Notifications
You must be signed in to change notification settings - Fork 808
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
Disable light client when fork epoch is misaligned #7022
base: release-v7.0.0
Are you sure you want to change the base?
Disable light client when fork epoch is misaligned #7022
Conversation
Oops, looks like you merged |
A |
4fa7acc
to
cedc381
Compare
lol thanks, apparently my subconscious needs to merge unstable |
I got scared by the size of the diff 😱 . Now it's fixed I can review 😌 |
LightClientFinalityUpdateError::Disabled | ||
| LightClientFinalityUpdateError::TooLate => debug!( | ||
self.log, | ||
":ight client finality update ignored"; |
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.
":ight client finality update ignored"; | |
"Light client finality update ignored"; |
&self, | ||
current_slot: Slot, | ||
) -> bool { | ||
let is_fork_boundary_inside_sync_committee_period = |fork_epoch: Epoch| { |
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.
There's an existing check below, but it only log a warning if it's misaligned. Perhaps we can remove that one given that it would be a bit more obvious now if the fork schedule is misaligned? (light client disabled)
lighthouse/beacon_node/src/lib.rs
Line 190 in a1b7d61
fn validator_fork_epochs(spec: &ChainSpec) -> Result<(), Vec<(ForkName, Epoch)>> { |
Closes #7002
Temporarily disables light client functionality when fork epoch is misaligned
Add metrics for Light client gossip verification failures. I've added two categories of errors
Failures
andIgnores
so we can differentiate between "real" failures and janky data. I've also added a new error typeTooLate
so that we dont include stale data as part of our "Failures" metrics. Ideally it'd be nice to have this included in the 7.0 release