-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
Fix logging context propagation #185
Conversation
Test Results 98 files + 64 98 suites +64 10m 27s ⏱️ + 10m 2s Results for commit 21cd9c8. ± Comparison against base commit f0981d2. This pull request removes 27 and adds 69 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for figuring this one out!
sdk-core/src/main/java/dev/restate/sdk/core/ExecutorSwitchingWrappers.java
Show resolved
Hide resolved
sdk-core/src/main/java/dev/restate/sdk/core/InvocationStateMachine.java
Outdated
Show resolved
Hide resolved
appender.testlogger.layout.pattern = %-4r %-5p %X [%t] %c:%L - %m%n |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
* This is now more obvious, in particular It makes more clear what's the boundary between state machine and user code and how the Context is propagated * Renamed the methods of RestateServerCallListener to make more clear their goal
Fix the LoggingContextSetter.THREAD_LOCAL_INSTANCE
14b0ce8
to
21cd9c8
Compare
Fix #180
The GrpcContextDataProvider was not wrong on itself, the problem was that we have to merge SPI files when creating the shadowJar. See apache/logging-log4j2#2099