tracing: drop GetHash().ToString() argument from the validation:block_connected
tracepoint
#23302
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.
The tracepoint
validation:block_connected
was introduced in #22006.The first argument was the hash of the connected block as a pointer
to a C-like String. The last argument passed the hash of the
connected block as a pointer to 32 bytes. The hash was only passed as
string to allow
bpftrace
scripts to print the hash. It was(incorrectly) assumed that
bpftrace
cannot hex-format and print theblock hash given only the hash as bytes.
The block hash can be printed in
bpftrace
by callingprintf("%02x")
for each byte of the hash in anunroll () {...}
.By starting from the last byte of the hash, it can be printed in
big-endian (the block-explorer format).
See also: #22902 (comment)
This is a breaking change to the block_connected tracepoint API, however
this tracepoint has not yet been included in a release.