-
Notifications
You must be signed in to change notification settings - Fork 3k
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
op-node: Use single option for peer scoring level #6001
Conversation
…p.scoring We don't need the complexity of supporting independent scoring setups for general peer behaviour and per-topic behaviour.
Simplify loading code with a switch instead of needing to build a map.
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## aj/optional-score-config #6001 +/- ##
============================================================
+ Coverage 40.66% 41.35% +0.68%
============================================================
Files 319 434 +115
Lines 26110 29552 +3442
Branches 0 713 +713
============================================================
+ Hits 10617 12220 +1603
- Misses 14515 16309 +1794
- Partials 978 1023 +45
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This PR has been added to the merge queue, and will be merged soon. |
This PR is next in line to be merged, and will be merged as soon as checks pass. |
✅ Deploy Preview for opstack-docs canceled.
|
Description
Simplify the peer scoring configuration.
ScoreParams
wrapper object that can benil
inp2p.Config
. This turned out to not be needed now since topic params have been folded into peer params, but will be useful again when application specific params are added for p2p sync. Aim here is that either all the params are set or none rather than having application specific score params set but scoring disabled.Metadata