Better handling of comma-separated CL_NODE#2658
Open
yorickdowne wants to merge 1 commit into
Open
Conversation
yorickdowne
force-pushed
the
multiple-cl-nodes
branch
from
3a00e30 to
5cd1d09
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What I did
Better UX for comma-separated
CL_NODEin more places.ethdonow finds a usableCL_NODE, as do keymanager and the legacy Lighthouse validator exit. Teku legacy exit uses a comma-separated list, and Siren uses the first entry in the list. I don't have curl in Siren to get fancier.(not mandatory) A picture of a cute animal, if possible in relation to what you did