You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a task in a wrapped executor, a new span should be created for the task. This will allow tracing information to clearly indicate when the task started and finished running in the executor.
Fixes#63
~This PR preserves the existing executor wrapping methods and their behavior. So users must explicitly opt-in to the new span-creating behavior.~
This is no longer true. The existing executor methods will now create a new span for tasks they run.
Each call to transform will create another nested span because the next callback is being enqueued inside the previous task. In this scenario it would be better to have no executor span to avoid this potentially long chain of nested spans.
When running a task in a wrapped executor, a new span should be created for the task. This will allow tracing information to clearly indicate when the task started and finished running in the executor.
See #59 (comment).
The text was updated successfully, but these errors were encountered: