-
Notifications
You must be signed in to change notification settings - Fork 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
ETCM-365: Version info in Hello.clientId #794
Conversation
c281d52
to
5210423
Compare
5210423
to
9684d23
Compare
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 didn't do as an elaborate normalisation as besu in the PlatformDetector, called from BesuInfo; seemed like an overkill.
Agree!
Apart from one comment LGTM!
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.
Apart from a last comment, LGTM!
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.
LGTM!
.\\ //.
. \ \ / /.
.\ ,\ /` /,.-
-. \ /'/ / .
` - `-' \ -
'. /.\`
- .-
:`//.'
.`.'
.' BP
Description
The PR adds the conventional Ethereum node name in the
WireProtocol.Hello.clientId
field, for example:mantis/v3.0-cd5ae33/linux-amd64/ubuntu-openjdk64bitservervm-java-11.0.9
.The
-Dmantis.client-identity
property can be used to splice a user identity into it to distinguish our client, perhaps by a ticket number or just belonging to an organisation.I didn't do as an elaborate normalisation as
besu
in thePlatformDetector
, called fromBesuInfo
; seemed like an overkill.