Skip to content
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] - Fix order of testnet config load #1558

Closed
wants to merge 1 commit into from

Conversation

pawanjay176
Copy link
Member

Issue Addressed

Fixes #1552

Proposed Changes

Earlier, we were always loading the hardcoded default testnet config which is a mainnet spec. So running lighthouse with --spec option anything other than mainnet gave errors because we tried loading a mainnet genesis spec with minimal/interop flags.

This PR fixes the order of loading such that we load the hardcoded default spec only if neither --testnet and --testnet-dir flags are present.

Copy link
Member

@AgeManning AgeManning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch!

@AgeManning
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Aug 21, 2020
## Issue Addressed

Fixes #1552 

## Proposed Changes

Earlier, we were always loading the hardcoded default testnet config which is a mainnet spec. So running lighthouse with `--spec` option anything other than mainnet gave errors because we tried loading a mainnet genesis spec with `minimal`/`interop` flags.

This PR fixes the order of loading such that we load the hardcoded default spec only if neither `--testnet` and `--testnet-dir` flags are present.
@bors
Copy link

bors bot commented Aug 21, 2020

Build failed:

@AgeManning
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Aug 25, 2020
## Issue Addressed

Fixes #1552 

## Proposed Changes

Earlier, we were always loading the hardcoded default testnet config which is a mainnet spec. So running lighthouse with `--spec` option anything other than mainnet gave errors because we tried loading a mainnet genesis spec with `minimal`/`interop` flags.

This PR fixes the order of loading such that we load the hardcoded default spec only if neither `--testnet` and `--testnet-dir` flags are present.
@bors bors bot changed the title Fix order of testnet config load [Merged by Bors] - Fix order of testnet config load Aug 25, 2020
@bors bors bot closed this Aug 25, 2020
@pawanjay176 pawanjay176 deleted the fix-minimal branch August 25, 2020 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants