-
Notifications
You must be signed in to change notification settings - Fork 809
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
[Merged by Bors] - handle peer state transitions on gossipsub score changes + refactoring #1892
[Merged by Bors] - handle peer state transitions on gossipsub score changes + refactoring #1892
Conversation
&mut self.events, | ||
&self.log, | ||
); | ||
if previous_state == info.score_state() { |
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.
Should this be a !=
?
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.
No this should really be an ==
. It was the else branch in the original code. Basically we log already a line inside handle_score_transitions
if the state changed. This line here is to log that the score changed if the state didn't change.
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.
Updated
bors r+ |
#1892) ## Issue Addressed NA ## Proposed Changes Correctly handles peer state transitions on gossipsub changes + refactors handling of peer state transitions into one function used for lighthouse score changes and gossipsub score changes. Co-authored-by: Age Manning <[email protected]>
Pull request successfully merged into master. Build succeeded: |
Issue Addressed
NA
Proposed Changes
Correctly handles peer state transitions on gossipsub changes + refactors handling of peer state transitions into one function used for lighthouse score changes and gossipsub score changes.