-
Notifications
You must be signed in to change notification settings - Fork 2k
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
LoggerFactory slf4j related regression fix #15659
Conversation
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.
@yazun The change looks good to me can you rebase your change against the branch rel-3.42.0
so we could release it ASAP?
Fix the regression that caused DRF loading fail due to spurious dependency on slf4j when log4j2 exists. Check for water logging availability was throwing exception if slf4j was not used while loading some models. this seems like a regression between 3.30 and 3.40. h2oai#6725
6d10f5b
to
49cb990
Compare
rebased to latest. I am on the road now with no local copy, so it might be done in 2 days or so. |
Hello @mn-mikke |
Dear @mmalohlava, would you have time to review this change? I work in the academic team with @yazun and currently we have a cumbersome workaround using a custom-build jar file by @yazun , but we would much prefer to migrate to the latest version that has this fix included. Best regards, and thanks! |
Fix the regression that caused DRF loading fail due to spurious dependency on slf4j when log4j2 exists. Check for water logging availability was throwing exception if slf4j was not used while loading some models. Seems like a regression between 3.30 and 3.40. #6725