Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Context propagation: use new APIs from latest snapshots #3256

Merged
merged 3 commits into from
Nov 2, 2022
Merged

Context propagation: use new APIs from latest snapshots #3256

merged 3 commits into from
Nov 2, 2022

Commits on Oct 27, 2022

  1. Depend on post-RC1 snapshots of context-propagation

    @simonbasle
    simonbasle committed Oct 27, 2022
    Configuration menu
    Copy the full SHA
    76c09c1 View commit details
    Browse the repository at this point in the history

  2. Use ContextSnapshot.setAllThreadLocalsFrom

    @simonbasle
    simonbasle committed Oct 27, 2022
    Configuration menu
    Copy the full SHA
    06fd8c1 View commit details
    Browse the repository at this point in the history

  3. Remove registry and intermediary classes, use Supplier<Context> 

    With the introduction of removal methods in ContextRegistry, it becomes
more practical to use the ContextRegistry.getInstance global instance.
Following that, two of the three intermediate classes are no longer
needed and can be replaced with lambdas: ContextCaptureFunction and
ContextRestoreHandleConsumer.

Instead of calling the ContextPropagation methods with a subscriber
(which necessitates some mocking in tests), we now take a Supplier
of Context. A CoreSubscriber::currentContext method reference can
do the trick in production code.
    @simonbasle
    simonbasle committed Oct 27, 2022
    Configuration menu
    Copy the full SHA
    4e9b856 View commit details
    Browse the repository at this point in the history