Add simple scope management whenever a context is attached #3159
+19
−7
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.
_SCOPES_KEY
that will hold a tuple of(curent_scope, isolation_scope)
current_scope
will always be forked (like on every span creation/context update in practice)attach
, so not on all copy-on-write context object creation but only on apis such astrace.use_span
ortracer.start_as_current_span
context
fork corresponds to ourcurrent_scope
forkisolation_scope
currently will not be forkedattach
function