gnosis/lighthouse
1
0
Fork 0
mirror of https://github.com/sigp/lighthouse.git synced 2026-05-08 01:05:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix tracing span for execution payload verif (#8419)

Browse Source 
Fix the span on execution payload verification (newPayload), by creating a new span rather than using the parent span. Using the parent span was incorrectly associating the time spent verifying the payload with `from_signature_verified_components`.


Co-Authored-By: Michael Sproul <michael@sigmaprime.io>
This commit is contained in:
Michael Sproul
2025-11-17 13:04:46 +11:00
committed by GitHub
parent 47b984e799
commit 01a654bfa8
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
beacon_node/beacon_chain/src/block_verification.rs
View File

@@ -1428,11 +1428,11 @@ impl<T: BeaconChainTypes> ExecutionPendingBlock<T> {
// Spawn the payload verification future as a new task, but don't wait for it to complete. // Spawn the payload verification future as a new task, but don't wait for it to complete.
// The `payload_verification_future` will be awaited later to ensure verification completed // The `payload_verification_future` will be awaited later to ensure verification completed
// successfully. // successfully.
let current_span = Span::current();
let payload_verification_handle = chain let payload_verification_handle = chain
.task_executor .task_executor
.spawn_handle( .spawn_handle(
payload_verification_future.instrument(current_span), payload_verification_future
.instrument(debug_span!("execution_payload_verification")),
"execution_payload_verification", "execution_payload_verification",
) )
.ok_or(BeaconChainError::RuntimeShutdown)?; .ok_or(BeaconChainError::RuntimeShutdown)?;