Record BEACON_BLOCK_DELAY_GOSSIP
metric only after a bock is verified
#6046
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.
@michaelsproul found that the
BEACON_BLOCK_DELAY_GOSSIP
metric is recorded before the block is verified:lighthouse/beacon_node/network/src/network_beacon_processor/gossip_methods.rs
Lines 910 to 919 in d84e3e3
This causes the metric could record a time in the range minutes-hours if an old block is received, see https://discord.com/channels/605577013327167508/746918775919738893/1255734712971038810
This PR fixes it so that the metric is only recorded after the block is verified.
Thanks @michaelsproul !