Remove PropagatingSupervisor #681
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
grouzen
previously approved these changes
May 6, 2023
dmytr
force-pushed
the
remove-propagating-supervisor
branch
from
9de8fde to
5e44d70
Compare
grouzen
approved these changes
May 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since version 1.25.0 OpenTelemetry JVM agent supports ZIO. There is no need to use
PropagatingSupervisornow.This PR:
PropagatingSupervisor.ContextStorage.threadLocaltoContextStorage.openTelemetryContextas it's a much more fitting name.Tracing.propagatingbecause now it's enough to useTracing.livein combination withContextStorage.openTelemetryContext.These are breaking changes, but since we are in RC phase, I hope this is acceptable.