-
-
Notifications
You must be signed in to change notification settings - Fork 306
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: parse --builder.boostFactor value as bigint instead of number #6277
Conversation
@@ -248,7 +248,7 @@ export const validatorOptions: CliCommandOptions<IValidatorCliArgs> = { | |||
}, | |||
|
|||
"builder.boostFactor": { | |||
type: "number", | |||
type: "string", |
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 does not look like yargs supports bigint based on yargs/yargs#440 and looking at type options.
@g11tech somewhat related to this, I noticed we are not supporting lodestar/packages/cli/src/util/proposerConfig.ts Lines 14 to 24 in e51f495
|
Performance Report✔️ no performance regression detected 🚀🚀 Significant benchmark improvement detected
Full benchmark results
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## unstable #6277 +/- ##
=========================================
Coverage 80.38% 80.38%
=========================================
Files 202 202
Lines 19622 19622
Branches 1176 1176
=========================================
Hits 15773 15773
Misses 3821 3821
Partials 28 28 |
yes can add in a followup 👍 |
🎉 This PR is included in v1.14.0 🎉 |
Motivation
Noticed another issue related to #6275, we parse the value of
--builder.boostFactor
as a number instead of bigint. We have to use string and parse it separately for the same reason as we do in on API level as otherwise we lose precision on the value.Description
Parse
--builder.boostFactor
value as bigint instead of number.