-
Notifications
You must be signed in to change notification settings - Fork 776
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
[Merged by Bors] - require http and metrics for respective flags #4674
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.
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.
Oh sorry, just realized we should probably make the same changes to beacon_node/src/cli.rs
?
yup makes sense Jimmy, updated! |
beacon_node/src/cli.rs
Outdated
@@ -316,22 +316,25 @@ pub fn cli_app<'a, 'b>() -> App<'a, 'b> { | |||
.arg( | |||
Arg::with_name("http-address") | |||
.long("http-address") | |||
.requires("http") |
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.
Hey sorry @jxs, I've just realized that http api can be enabled via --staking
or --gui
as well, so --http
is not strictly necessary, so this may be a breaking change for the beacon node, and we might want to leave this unchnaged?
lighthouse/beacon_node/src/config.rs
Lines 88 to 91 in d61f507
if cli_args.is_present("staking") { | |
client_config.http_api.enabled = true; | |
client_config.sync_eth1_chain = true; | |
} |
lighthouse/beacon_node/src/config.rs
Lines 810 to 813 in d61f507
if cli_args.is_present("gui") { | |
client_config.http_api.enabled = true; | |
client_config.validator_monitor_auto = true; | |
} |
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.
btw I discovered this from the failing doppelganger
tests, it uses --staking
instead of --http
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.
thanks for digging it Jimmy! I updated with a ArgGroup
for http
, gui
and staking
, when one of them is missing the following error is displayed:
error: The following required arguments were not provided:
<--http|--gui|--staking>
Do you think it's clear enough? If not I can revert, meanwhile the doppelganger
tests are still failing, can you access the logs? I am able to run the beacon_node
for them locally but get a jwt validation error 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.
ok managed to fix the doppelganger protection tests
and it seems to me it's mo longer a breaking change since all the flags still work as only one of the three is required, but ptal Jimmy
Marking this as |
to both add default values and then require them, fixes doppelganger protection test
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.
Nice! Let's merge
bors r+ |
## Issue Addressed following discussion on #4639 (comment) this PR makes the `http` and `metrics` sub-flags to require those main flags enabled
Build failed (retrying...): |
## Issue Addressed following discussion on #4639 (comment) this PR makes the `http` and `metrics` sub-flags to require those main flags enabled
Build failed (retrying...): |
bors r- |
Canceled. |
## Issue Addressed following discussion on #4639 (comment) this PR makes the `http` and `metrics` sub-flags to require those main flags enabled
This PR was included in a batch that was canceled, it will be automatically retried |
## Issue Addressed following discussion on #4639 (comment) this PR makes the `http` and `metrics` sub-flags to require those main flags enabled
Pull request successfully merged into unstable. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page.
|
## Issue Addressed Fixes breaking change introduced on #4674 that doesn't allow multiple `http_enabled` `ArgGroup` flags
## Issue Addressed Fixes breaking change introduced on #4674 that doesn't allow multiple `http_enabled` `ArgGroup` flags
## Issue Addressed Fixes breaking change introduced on #4674 that doesn't allow multiple `http_enabled` `ArgGroup` flags
## Issue Addressed following discussion on sigp#4639 (comment) this PR makes the `http` and `metrics` sub-flags to require those main flags enabled
## Issue Addressed Fixes breaking change introduced on sigp#4674 that doesn't allow multiple `http_enabled` `ArgGroup` flags
## Issue Addressed following discussion on sigp#4639 (comment) this PR makes the `http` and `metrics` sub-flags to require those main flags enabled
## Issue Addressed Fixes breaking change introduced on sigp#4674 that doesn't allow multiple `http_enabled` `ArgGroup` flags
## Issue Addressed following discussion on sigp#4639 (comment) this PR makes the `http` and `metrics` sub-flags to require those main flags enabled
## Issue Addressed Fixes breaking change introduced on sigp#4674 that doesn't allow multiple `http_enabled` `ArgGroup` flags
Issue Addressed
following discussion on #4639 (comment) this PR makes the
http
andmetrics
sub-flags to require those main flags enabled