-
Notifications
You must be signed in to change notification settings - Fork 11
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
Ping multisig #137
Ping multisig #137
Conversation
Multisig bool | ||
EthClientConnected bool |
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.
do we need both? isn't it enough just multisig? it won't be working without eth, right ?
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.
we check connection to eth client when start operator, if no it cant start, but we can loose it after we started. So we can be Multisig=true
and EthClientConnected=false
.
For old operator versions we dont have both fields so it will be false
, false
.
If we have only EthClientConnected then we cant distinguish between old and new version, only comparing version
. So Multisig
is rather informational for users not to compare versions, as old will be always false
Please let me know if it makes sense.
for _, s := range servers { | ||
ips = append(ips, s.HttpSrv.URL) | ||
} | ||
require.NoError(t, err) |
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.
what err are you checking?
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.
removed
Closes #128
pong
to include fieldsMultisig
,EthClientConnected