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] - Shift networking configuration #4426

Conversation

armaganyildirak
Copy link
Member

Issue Addressed

Addresses #4401

Proposed Changes

Shift some constants into ChainSpec and remove the constant values from code space.

Additional Info

I mostly used MainnetEthSpec::default_spec() for getting ChainSpec. I wonder Did I make a mistake about that.

@CLAassistant
Copy link

CLAassistant commented Jun 22, 2023

CLA assistant check
All committers have signed the CLA.

@divagant-martian
Copy link
Collaborator

divagant-martian commented Jun 22, 2023

In most of these places (if not all, haven't check) you probably want to access the chain spec we already have. Left an example above, but @pawanjay176 prob has better pointers (and more time to put into the review)

Copy link
Member

@pawanjay176 pawanjay176 left a comment

Choose a reason for hiding this comment

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

Initial review. Looking good, need to change a couple occurrences of default_spec to using the actual ChainSpec object.

beacon_node/beacon_chain/src/attestation_verification.rs Outdated Show resolved Hide resolved
beacon_node/beacon_chain/src/block_verification.rs Outdated Show resolved Hide resolved
beacon_node/lighthouse_network/src/config.rs Outdated Show resolved Hide resolved
beacon_node/lighthouse_network/src/config.rs Outdated Show resolved Hide resolved
beacon_node/lighthouse_network/src/rpc/handler.rs Outdated Show resolved Hide resolved
consensus/types/src/chain_spec.rs Show resolved Hide resolved
Copy link
Collaborator

@divagant-martian divagant-martian left a comment

Choose a reason for hiding this comment

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

Haven't finished the review, but found some time to give this a check

.vscode/settings.json Outdated Show resolved Hide resolved
beacon_node/beacon_chain/src/attestation_verification.rs Outdated Show resolved Hide resolved
beacon_node/lighthouse_network/src/config.rs Outdated Show resolved Hide resolved
beacon_node/lighthouse_network/src/rpc/protocol.rs Outdated Show resolved Hide resolved
beacon_node/lighthouse_network/src/rpc/handler.rs Outdated Show resolved Hide resolved
Copy link
Collaborator

@divagant-martian divagant-martian left a comment

Choose a reason for hiding this comment

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

@armaganyildirak has addressed the last bug I found and the pr is self-consistent now. LGTM

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.

Ok. Lets get this in.

@AgeManning
Copy link
Member

bors r+

@AgeManning AgeManning added ready-for-merge This PR is ready to merge. and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. labels Aug 1, 2023
bors bot pushed a commit that referenced this pull request Aug 1, 2023
## Issue Addressed
Addresses [#4401](#4401)

## Proposed Changes
Shift some constants into ```ChainSpec``` and remove the constant values from code space.

## Additional Info

I mostly used ```MainnetEthSpec::default_spec()``` for getting ```ChainSpec```. I wonder Did I make a mistake about that.


Co-authored-by: armaganyildirak <armaganyildirak@gmail.com>
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: Age Manning <Age@AgeManning.com>
Co-authored-by: Diva M <divma@protonmail.com>
@bors
Copy link

bors bot commented Aug 2, 2023

Build failed:

@divagant-martian
Copy link
Collaborator

divagant-martian commented Aug 2, 2023

weird that this failed in bors but not in the last commit. @paulhauner is this some kind of random failure? it looks kinda deterministic? or any ideas in general?
context

@paulhauner
Copy link
Member

paulhauner commented Aug 2, 2023

Hmm, a bunch of slashing protection tests started failing all with the same error:

---- attestation_tests::valid_empty_history stdout ----
thread 'attestation_tests::valid_empty_history' panicked at 'called `Result::unwrap()` on an `Err` value: SQLError("Unable to open database: Error(None)")', validator_client/slashing_protection/src/test_utils.rs:80:71

There's some conflicts to fix.. Maybe we can see how CI goes after they're fixed?

@paulhauner
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Aug 2, 2023
## Issue Addressed
Addresses [#4401](#4401)

## Proposed Changes
Shift some constants into ```ChainSpec``` and remove the constant values from code space.

## Additional Info

I mostly used ```MainnetEthSpec::default_spec()``` for getting ```ChainSpec```. I wonder Did I make a mistake about that.


Co-authored-by: armaganyildirak <armaganyildirak@gmail.com>
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: Age Manning <Age@AgeManning.com>
Co-authored-by: Diva M <divma@protonmail.com>
@bors
Copy link

bors bot commented Aug 2, 2023

Build failed (retrying...):

bors bot pushed a commit that referenced this pull request Aug 2, 2023
## Issue Addressed
Addresses [#4401](#4401)

## Proposed Changes
Shift some constants into ```ChainSpec``` and remove the constant values from code space.

## Additional Info

I mostly used ```MainnetEthSpec::default_spec()``` for getting ```ChainSpec```. I wonder Did I make a mistake about that.


Co-authored-by: armaganyildirak <armaganyildirak@gmail.com>
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: Age Manning <Age@AgeManning.com>
Co-authored-by: Diva M <divma@protonmail.com>
@bors
Copy link

bors bot commented Aug 2, 2023

Build failed (retrying...):

bors bot pushed a commit that referenced this pull request Aug 3, 2023
## Issue Addressed
Addresses [#4401](#4401)

## Proposed Changes
Shift some constants into ```ChainSpec``` and remove the constant values from code space.

## Additional Info

I mostly used ```MainnetEthSpec::default_spec()``` for getting ```ChainSpec```. I wonder Did I make a mistake about that.


Co-authored-by: armaganyildirak <armaganyildirak@gmail.com>
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: Age Manning <Age@AgeManning.com>
Co-authored-by: Diva M <divma@protonmail.com>
@bors
Copy link

bors bot commented Aug 3, 2023

Build failed:

@AgeManning
Copy link
Member

bors has chosen violence today.

bors retry

bors bot pushed a commit that referenced this pull request Aug 3, 2023
## Issue Addressed
Addresses [#4401](#4401)

## Proposed Changes
Shift some constants into ```ChainSpec``` and remove the constant values from code space.

## Additional Info

I mostly used ```MainnetEthSpec::default_spec()``` for getting ```ChainSpec```. I wonder Did I make a mistake about that.


Co-authored-by: armaganyildirak <armaganyildirak@gmail.com>
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: Age Manning <Age@AgeManning.com>
Co-authored-by: Diva M <divma@protonmail.com>
@bors
Copy link

bors bot commented Aug 3, 2023

@bors bors bot changed the title Shift networking configuration [Merged by Bors] - Shift networking configuration Aug 3, 2023
@bors bors bot closed this Aug 3, 2023
@realbigsean realbigsean mentioned this pull request Oct 12, 2023
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
Addresses [sigp#4401](sigp#4401)

Shift some constants into ```ChainSpec``` and remove the constant values from code space.

I mostly used ```MainnetEthSpec::default_spec()``` for getting ```ChainSpec```. I wonder Did I make a mistake about that.

Co-authored-by: armaganyildirak <armaganyildirak@gmail.com>
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: Age Manning <Age@AgeManning.com>
Co-authored-by: Diva M <divma@protonmail.com>
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
Addresses [sigp#4401](sigp#4401)

Shift some constants into ```ChainSpec``` and remove the constant values from code space.

I mostly used ```MainnetEthSpec::default_spec()``` for getting ```ChainSpec```. I wonder Did I make a mistake about that.

Co-authored-by: armaganyildirak <armaganyildirak@gmail.com>
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: Age Manning <Age@AgeManning.com>
Co-authored-by: Diva M <divma@protonmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge This PR is ready to merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants