tracing: fix spawn_blocking
location fields
#5573
Merged
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.
Motivation
In a previous PR (#4128), the
spawn.location
field on task spans wasstructured into 3 separate fields for the
file
,line
, andcol
.There is a separately created span for blocking tasks which was missed.
This caused tasks created with
spawn_blocking
to appear intokio-console
without a location, but with an additional "free form"field containing the formatted source code location.
Solution
This change modifies this span to use the same format. The span creation
needs to be separate from the other task spans because it records the
function name. This information is useful in the
spawn_blocking
case,but can be "catastrophically long" in the
async fn
case and wasremoved in #3074.