Pratik Mankawde 59bae37688 fix(telemetry): nest the accept work under consensus.accept.apply ...

accept.apply was a plain SpanGuard, so it never became the ambient span of
doAccept. The spans the function goes on to create inherited the activated
accept span instead and came out as accept.apply's siblings, while running
inside its own time window. Every guard was scoped before the SpanGuard split,
so this restores the hierarchy that design had.

Scoped now, so the hierarchy follows the call flow. Drops the parent-context
fallback arm with it: the accept context is captured only while the accept span
is live, and that span is a child of the round context, so an invalid accept
context implies an invalid round context and both arms returned an empty guard.

2026-09-23 13:49:42 +01:00

..

xrpl

fix(telemetry): nest the accept work under consensus.accept.apply

2026-09-23 13:49:42 +01:00