-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
passes through feature-set to gossip requests handling #12878
Conversation
48747f1
to
4a9d5c8
Compare
Codecov Report
@@ Coverage Diff @@
## master #12878 +/- ##
=========================================
- Coverage 81.9% 81.9% -0.1%
=========================================
Files 360 361 +1
Lines 84925 85057 +132
=========================================
+ Hits 69580 69682 +102
- Misses 15345 15375 +30 |
core/src/cluster_info.rs
Outdated
bank_forks | ||
.read() | ||
.unwrap() | ||
.working_bank() |
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.
It'll be better to use .root_bank()
. With the .working_bank()
, we could see a feature get enabled and then disabled again (if the feature happens to get enabled in a minority fork). Otherwise lgtm!
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.
done.
There are other places in this file which are using .working_bank
(e.g. for stakes). Do you think they should also use .root_bank
instead?
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.
I'd say so, but only for consistency. It looks like it shouldn't matter in practice either way though
4a9d5c8
to
b9eff5b
Compare
b9eff5b
to
de9681d
Compare
…2878) * passes through feature-set to down to gossip requests handling * takes the feature-set from root_bank instead of working_bank
* passes through feature-set to down to gossip requests handling * takes the feature-set from root_bank instead of working_bank (cherry picked from commit 4828316)
* passes through feature-set to down to gossip requests handling * takes the feature-set from root_bank instead of working_bank (cherry picked from commit 4828316)
* passes through feature-set to down to gossip requests handling * takes the feature-set from root_bank instead of working_bank (cherry picked from commit 4828316)
* passes through feature-set to down to gossip requests handling * takes the feature-set from root_bank instead of working_bank (cherry picked from commit 4828316) Co-authored-by: behzad nouri <[email protected]>
* passes through feature-set to down to gossip requests handling * takes the feature-set from root_bank instead of working_bank (cherry picked from commit 4828316)
* passes through feature-set to down to gossip requests handling * takes the feature-set from root_bank instead of working_bank (cherry picked from commit 4828316) Co-authored-by: behzad nouri <[email protected]>
Problem
For #12794 we want to activate ping/pong check of addresses dynamically once super majority of nodes have updated to the new code. see: #12794 (comment)
Summary of Changes
The commit adds a new feature id for ping/pong check and passes through the feature-set construct down to request handler.