We have an issue that tracing spans from previous queries occurring in new queries.
🔍 What does this change?
When Span::enter() is called and the returned Drop-guard is kept over an .await point it's possible that this results in wrong traces. For more information see the Span::enter() documentation. This PR avoids calling .enter() in async context and uses the Instrument trait instead.
Pre-Merge Checklist 🚀
🚢 Has this modified a publishable library?
This PR:
[x] does not modify any publishable blocks or libraries, or modifications do not need publishing
🌟 What is the purpose of this PR?
We have an issue that tracing spans from previous queries occurring in new queries.
🔍 What does this change?
When
Span::enter()
is called and the returnedDrop
-guard is kept over an.await
point it's possible that this results in wrong traces. For more information see theSpan::enter()
documentation. This PR avoids calling.enter()
inasync
context and uses theInstrument
trait instead.Pre-Merge Checklist 🚀
🚢 Has this modified a publishable library?
This PR:
📜 Does this require a change to the docs?
The changes in this PR:
🕸️ Does this require a change to the Turbo Graph?
The changes in this PR: