-
Notifications
You must be signed in to change notification settings - Fork 747
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
Fix bug in --builder-proposals
#5151
Conversation
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.
Looks good! Thanks for the fix.
Pushed a fix for the duplicate test case as discussed.
Thanks for noticing & fixing the test. I pushed a new commit to get cargo fmt passing. Let's merge |
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
@Mergifyio refresh |
✅ Pull request refreshed |
@Mergifyio requeue |
❌ This pull request head commit has not been previously disembarked from queue. |
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at d2aef1b |
* Fix bug in `--builder-proposals` * Add tests * More sensible test order * Fix duplicate builder-boost test case * Cargo fmt and rename
Issue Addressed
The validator client was using the wrong logic for the default
builder_boost_factor
when the--builder-proposals
flag was provided. Rather than setting the boost to 0 whenbuilder-propsals
was false, it was setting it to 0 whenbuilder-proposals
was true.Proposed Changes