Skip to content

Show error when both use-native-reth secondary-el flags are enabled #75

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

Closed
wants to merge 4 commits into from

Conversation

simon0x1800
Copy link

Handles issue #59 by panicing when both flags are enabled. @ferranbt

@ferranbt
Copy link
Collaborator

Thank you for the PR! The idea for the issue is that they should work togheter.

@simon0x1800
Copy link
Author

Hey @ferranbt can you take a look now?

@@ -62,8 +62,16 @@ func (l *L1Recipe) Apply(ctx *ExContext, artifacts *Artifacts) *Manifest {
// we are going to use the cl-proxy service to connect the beacon node to two builders
// one the 'el' builder and another one the remote one
elService = "cl-proxy"

primaryBuilder := "el"
if l.useNativeReth {
Copy link
Collaborator

Choose a reason for hiding this comment

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

This should be happening already because the docker runtime should resolve this reference.

@ferranbt
Copy link
Collaborator

Actually, I checked again and this problem does not show up anymore. I think it was fixed with #50

@ferranbt ferranbt closed this Mar 28, 2025
@simon0x1800 simon0x1800 deleted the l1-incompatible-flags branch April 4, 2025 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants