-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
feat: add builder selection executionalways #6370
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## unstable #6370 +/- ##
============================================
+ Coverage 60.14% 60.15% +0.01%
============================================
Files 407 407
Lines 46490 46506 +16
Branches 1545 1548 +3
============================================
+ Hits 27960 27975 +15
- Misses 18498 18499 +1
Partials 32 32 |
36ee1ec
to
093a287
Compare
Performance Report✔️ no performance regression detected Full benchmark results
|
case "executiononly": | ||
break; | ||
default: | ||
throw new YargsError("Invalid input for builder selection, check help"); | ||
throw Error("Invalid input for builder selection, check help"); |
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.
Any reason for abandoning YargsError
? I see it being used extensively in cli
package
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 changed those to YargsError
in #6332 but we reuse it now for validation of proposer settings file in #6357.
The main reason to use YargsError
is to have a cleaner error if a cli arg is incorrect as it does not include a stack trace but this error can now be thrown in multiple places and imo it's better to have a stack trace now.
🎉 This PR is included in v1.16.0 🎉 |
Motivation
executionalways
#6305Description
Adds builder selection
--builder.selection=executionalways
as an alias of--builder.boostFactor=0
Closes #6305