-
Notifications
You must be signed in to change notification settings - Fork 39
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
added build_version label to gossip handshake (BFT-502) #185
Conversation
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.
Looks good but I would implement some protection against spam, like a semver or length limit
I had to do a similar addition once to an Ethereum client, the format included the executable name, the platform and architecture and the version, eg. mantis/v3.0-cd5ae33/linux-amd64/ubuntu-openjdk64bitservervm-java-11.0.9
We don’t have multiple clients but I wouldn’t let anyone send unconstrained strings
The string is constrained by the Handshake message size. We will restrict it further if the need arises. |
It will allow us to monitor which nodes are using which version of the binary.
I've added a metric to count peers by their version (it is unbounded though).
I've added it to the http page display as well.
unrelated: I've removed Default impl for committees - it was creating invalid object.
unrelated: Exposed the validator::ProofOfPossession type.