propagate spans to tasks spawned by Hyper #550
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.
Previously, in the
futures
0.1 version of the proxy, we providedhyper
with a custom executor to propagatetracing
spans to tasksspawned by
hyper
. In the process of updating the proxy tostd::future
, this was removed, meaning that any tasks spawned by hyperare missing their spans. This makes events recorded by
h2
and so onhard to debug, especially when many connections are open.
This branch fixes this by adding an implementation of
hyper::Executor
that propagates the current span when spawning a task.
Signed-off-by: Eliza Weisman eliza@buoyant.io