-
Notifications
You must be signed in to change notification settings - Fork 109
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
hotfix(el/cl): allow multi clients to start if at least one node is up #2000
Merged
Merged
Changes from all commits
Commits
Show all changes
44 commits
Select commit
Hold shift + click to select a range
4a7ed06
do not crash if one client fails version check
y0sher 1784907
fix help note on multiple addresses
y0sher 6139748
don't compare genensis values
y0sher 54f982f
remove old assertSameGenesis code
y0sher 7a4248d
beacon/goclient: set up connection hooks, assert genesis
nkryuchkov 1025641
beacon/goclient: remove outdated comment
nkryuchkov af5c455
eth/executionclient: allow starting with unhealthy client
nkryuchkov 3b9efcf
eth/executionclient: simplify mutex usage
nkryuchkov c6592ad
eth/executionclient: fix tests for assertSameChainID
nkryuchkov b21c110
eth/executionclient: improve comment for assertSameGenesis
nkryuchkov 902c99a
handle nil genesis and chain ID responses
nkryuchkov 13edb6a
Merge branch 'stage' into fix/multiclient-oneclient
nkryuchkov e1cc2e3
refactor(multi_client): replace connectedCount atomic int with bool. …
y0sher 2bdc1ac
clarify comment
nkryuchkov 8db421f
fix double mutex lock
nkryuchkov 0dd1027
fix potential nil pointer dereference
nkryuchkov 8452bf4
check only genesis fork version instead of whole genesis
nkryuchkov d5fed41
create getClient helper method
nkryuchkov 75e2753
improve logs
nkryuchkov 999608b
fix issue with log fields
nkryuchkov 66d5051
atomic chain ID
nkryuchkov 61874f7
fix comment for client mutexes
nkryuchkov 70594e8
no nil assignment in Close
nkryuchkov 3cc71cd
add panic hook
nkryuchkov 7dd5aa0
attempt to fix panic
nkryuchkov ab91668
fix logging
nkryuchkov 99405c9
iterate clients forever in StreamLogs
nkryuchkov 768665d
set follow distance to 1
nkryuchkov 6af3463
Revert "set follow distance to 1"
nkryuchkov e9f5c7b
delete healthy channel
nkryuchkov f093561
remove obsolete tests
nkryuchkov 7b3a1f5
add successful call log
nkryuchkov 16dc397
fix potential nil ptr dereference
nkryuchkov 95af801
go-eth2-client: use fork with sync distance tolerance
nkryuchkov 411f482
add a comment about using github.com/nkryuchkov/go-eth2-client
nkryuchkov cbd61f5
code review comments
nkryuchkov f8188c6
named consensus client logger
nkryuchkov 5b72d6a
remove trace logs
nkryuchkov 77ca3cf
fix a typo
nkryuchkov 0406ad3
add a comment with execution client shutdown scenarios
nkryuchkov 23d393d
improve the comment for the call method
nkryuchkov 85779ec
Merge branch 'stage' into fix/multiclient-oneclient
nkryuchkov c890973
log client address on submissions
nkryuchkov 4751783
improve logs
nkryuchkov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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.
Not really specific to this PR but we often (and here as well) do 2 "duplicate" things
maybe would be simpler to just return
error
(with formatted withfmt.Errorf
to provide the necessary context) in places like this, bringing it up so we can get on the same page (whether we want to keep an eye on things like this or not)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.
The main difference and issue is that when logging with zap and adding fields its easy to search them by the label value. we'll need to squeeze everything to the
fmt.Errorf
, it'll still be searchable, but not by label.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.
I agree that we could think more about our logging approach, but I think this package currently uses logging in a way similar to other packages. If we decide to improve logging (e.g. use custom error types with fields), we need to do it project-wide