-
Notifications
You must be signed in to change notification settings - Fork 36
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
Move logging configuration to beginning of call() method #233
Move logging configuration to beginning of call() method #233
Conversation
This ensures that the correct log level is set before OpenCV is loaded.
75cc25a adds one more potential fix to address the illegal access warning logged to stderr, as noted by @erindiel :
The full stack trace, which results from setting
This warning only shows up when a memo file is loaded, so either the memo file must exist prior to conversion or multiple workers need to be used in order to see the warning. EsotericSoftware/reflectasm#64 and EsotericSoftware/kryo#692 are relevant upstream issues. From what I can tell (based on this documentation in particular), |
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.
With this PR, OpenCV warnings are no longer logged when using --log-level ERROR
and illegal access warnings are removed regardless of log level. 👍🏻
Unfortunately, 75cc25a seems to have caused regression on JDK 8 runtime environments when using the 0.9.0 distribution bundle - see #237 Reproduced locally
|
This ensures that the correct log level is set before OpenCV is loaded.
Compare using
--log-level ERROR
with and without this PR.