-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Conversation
@gavofyork I'm probably not the best person to review this impartially as Peter and I made these fixes together |
@@ -107,14 +107,14 @@ impl ValidatorSet for ValidatorContract { | |||
fn report_malicious(&self, address: &Address, _set_block: BlockNumber, block: BlockNumber, proof: Bytes) { | |||
match self.provider.report_malicious(&*self.transact(), *address, block.into(), proof).wait() { | |||
Ok(_) => warn!(target: "engine", "Reported malicious validator {}", address), | |||
Err(s) => warn!(target: "engine", "Validator {} could not be reported {}", address, s), | |||
Err(_) => {} // warn!(target: "engine", "Validator {} could not be reported {}", address, s), |
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.
Reason for warning removal?
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.
good catch. it was removed before because the checks weren't in place and it made testing very spammy
@rphmeier doesn't build |
ec4bf60
to
ad7507c
Compare
Added a few more commits to address two issues:
I would suggest keeping the additional flush for now since it's very rare, but then we can adjust |
Generate proof on uncommitted state and dont report skipped proposer if not signer.
Also prevents re-sealing on same step when validator set changes.