impl(otel): propagate OTelContext #12915
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.
Part of the work for #12880
Reimplement
CallContext
to use ourOTelContext
instead of using the active span.Our current implementation produces traces that look sorta correct. But it has problems, as described in the parent issue. This PR breaks the output that "looks sorta correct".
I talked with @alevenberg and we deemed this approach preferable to sending a mega-PR with GAPIC, handwritten library changes. (As long as the issue gets resolved by the next release.)
We remove the "call span active throughout" tests in the async retry loops because it is not something the retry class is doing. That is a property of the async operations, e.g.
AsyncUnaryRpcFuture
.Update ABI dumps because we have a false positive on missing templates for types that we don't even own:
This change is