mirror of
https://github.com/XRPLF/rippled.git
synced 2026-09-28 15:58:07 +00:00
f40c17a7ed
TxQ::accept set two of its per-transaction span attributes unconditionally, so every queued transaction the loop tried to apply to the open ledger paid for a 64-char string built from the transaction id and a transToken() lookup that builds a string, whether or not anything recorded them. That is once per candidate clearing the required fee level, on every ledger close. Guard both on the span being active, as the enqueue path in TxQ::apply and the apply-pipeline spans already do. The transaction apply itself stays outside the guard; only the attribute that reads its result is telemetry.