-
Notifications
You must be signed in to change notification settings - Fork 74.7k
Setting Log Level via Java API? #33881
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
Comments
Active development on the TF Java API is happening on https://github.com/tensorflow/java, might be worth opening the issue there. |
Hey, thanks, but the code in that repository is not yet available as a maven artifact. The relevant code in my case is hosted in https://github.com/tensorflow/tensorflow/tree/master/tensorflow/java |
Yes, but there isn't any development happening on the API in the main tensorflow tree. I don't think it's possible to set the log level from Java at the moment. Open the issue on the Java API and we'll get to it. |
Ok, done: tensorflow/java#3 |
Can we close issue here and follow up in tensorflow/java#3 .Please, confirm.Thanks! |
Whatever is easiest for you. |
Hi There, We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help. This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information. |
I don't think this has been resolved in tensorflow 2.X, or am I missing something? |
System information
Describe the current behavior
When using the current Java bindings for TensorFlow, the log gets filled with output from every operation when a model is evaluated. I was unable to find a way to set the log level via the Java API. Is this at all possible?
The text was updated successfully, but these errors were encountered: