-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
WARNING:root:Limited tf.compat.v2.summary API due to missing TensorBoard installation #2968
Comments
Hi @dproctor! Can you clarify: despite the warnings, does TensorBoard
Ideally, yeah, we wouldn’t have these warnings—just trying to narrow If TensorBoard doesn’t actually launch, what does it do? Could you post |
Thanks for the quick response! I assumed there was an issue when I saw the warnings and some other github issues referencing these warnings, but, now that I actually poke around with it, it does seem to behave as expected. So, I think this is really is just a question of annoying spurious warnings. While it'd be nice to resolve the underlying issue, an easier fix that would have saved me some time would have been if the development instructions were a little more thorough and told the user to expect this. More generally, I'd love to see other development tips on there, if they exist. For example, is there an easy way to get hot reloading of frontend resources with the bazel config? |
Looked into this briefly. The warnings are correct: the A patch that suffices to silence the warnings is: diff --git a/tensorboard/BUILD b/tensorboard/BUILD
index a40ff1e8..f4f72841 100644
--- a/tensorboard/BUILD
+++ b/tensorboard/BUILD
@@ -28,6 +28,8 @@ py_binary(
":program",
"//tensorboard:expect_tensorflow_installed",
"//tensorboard/plugins:base_plugin",
+ "//tensorboard/summary",
+ "//tensorboard/summary:tf_summary",
"//tensorboard/uploader:uploader_main_lib",
"//tensorboard/util:tb_logging",
], This is a bit weird in that the summaries are never actually required,
Absolutely; I’ll send a PR out presently. Thanks for this feedback. edit: #2972 |
If you’re editing one of TensorBoard’s core plugins, like the scalars diff --git a/tensorboard/components/BUILD b/tensorboard/components/BUILD
index 43b1634b..ccf6e5b4 100644
--- a/tensorboard/components/BUILD
+++ b/tensorboard/components/BUILD
@@ -19,7 +19,7 @@ tf_web_library(
tensorboard_html_binary(
name = "index",
- compile = True,
+ compile = False,
input_path = "/tensorboard.html",
output_path = "/index.html",
js_path = "/index.js", …which will work fine for most plugins, but break some, like the What-If Now, if you’re working on a new plugin, we encourage you to package and |
Great, thanks for the pointers! Dynamic plugins are exactly what I was looking for :) I could probably have found that on my own by spending a little more time digging through the code rather than depending on the documentation, but FWIW, it would have been more discoverable with an explicit mention of the plugin framework in the main README.md or DEVELOPMENT.md. |
this problem appears when i install tensorflow or keras in jupyter . |
For TF 2.1.0, install |
It may also due to the version of tensorboard diverses from the tensorflow version. |
This eliminated the warning for me:
I now have tensorflow version 2.4.1 and tensorboard version 2.5.0 |
|
I am unable to build and run TensorBoard from source with bazel. Doing so gives
the warning that the TensorBoard installation is missing (see output in repro
steps).
I'm following the development instructions.
Other issues and the diagnostics output suggest that the issue is with running TensorBoard from the source tree, but that's exactly what I want to do, i.e. make and run local modifications to TensorBoard.
What have I got wrong here?
Thanks!
Environment information (required)
Diagnostics
Diagnostics output
Suggestion: Avoid
tensorboard
packages without genfilesYour Python path contains a
tensorboard
package that does notinclude generated files. This can happen if your current directory
includes the TensorBoard source tree (e.g., you are in the TensorBoard
Git repository). The following directories from your Python path may
be problematic:
Next steps
Please try each suggestion enumerated above to determine whether it
solves your problem. If none of these suggestions works, please copy
ALL of the above output, including the lines containing only
backticks, into your GitHub issue or comment. Be sure to redact any
sensitive information.
Steps to reproduce (required)
The text was updated successfully, but these errors were encountered: