Bumping slf4j-api to 2.0.16 - #1706
Merged
Merged
Conversation
This may be the root cause of the logging issue I'm running into with Flux - at least according to https://www.slf4j.org/codes.html#StaticLoggerBinder , as I verified that slf4j-api 1.x is sneaking onto the classpath. This should otherwise be a no-op for all of the Java Client, it doesn't care what version of slf4j-api it's using.
BillFarber
approved these changes
Oct 7, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This may be the root cause of the logging issue I'm running into with Flux - at least according to https://www.slf4j.org/codes.html#StaticLoggerBinder , as I verified that slf4j-api 1.x is sneaking onto the classpath. This should otherwise be a no-op for all of the Java Client, it doesn't care what version of slf4j-api it's using.