Skip to content
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

Tensorboard not working in Google Colab anymore | ValueError: Duplicate plugins for name whatif #3481

Closed
ghost opened this issue Apr 5, 2020 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 5, 2020

Please be so kind to delete this issue for me, thank you in advance.

@wchargin
Copy link
Contributor

wchargin commented Apr 5, 2020

Hi @jandevries123! Thanks for the report. Yes, this is a known issue
with %tensorflow_version 1.x in Colab. We’re working on a patch to the
What-If Tool to resolve this; you can follow #3460 for updates. In the
meantime, a workaround is to uninstall the tensorboard-plugin-wit
package in Colab:

!pip uninstall -y tensorboard-plugin-wit

(This should work even if you are using the What-If Tool with
TensorBoard 1.x.)

@wchargin
Copy link
Contributor

wchargin commented Apr 5, 2020

Duplicate of #3460

@wchargin wchargin marked this as a duplicate of #3460 Apr 5, 2020
@wchargin wchargin closed this as completed Apr 5, 2020
wchargin added a commit that referenced this issue May 6, 2020
Summary:
Issues like #3460, #3481, and #3592 are all caused by an incompatibility
between certain versions of TensorBoard and the standalone What-If Tool.
This patch adds a check to the diagnosis script to warn accordingly.

Test Plan:
Install `tensorflow==2.1.0 tensorboard-plugin-wit==1.6.0.post2` into a
new virtualenv, and note that TensorBoard fails to start. Then run the
diagnosis script and note that it prints a suggestion with a command
that, when executed, solves the problem.

wchargin-branch: diagnose-broken-wit
wchargin added a commit that referenced this issue May 6, 2020
Summary:
Issues like #3460, #3481, and #3592 are all caused by an incompatibility
between certain versions of TensorBoard and the standalone What-If Tool.
This patch adds a check to the diagnosis script to warn accordingly.

Test Plan:
Install `tensorflow==2.1.0 tensorboard-plugin-wit==1.6.0.post2` into a
new virtualenv, and note that TensorBoard fails to start. Then run the
diagnosis script and note that it prints a suggestion with a command
that, when executed, solves the problem.

wchargin-branch: diagnose-broken-wit
caisq pushed a commit to caisq/tensorboard that referenced this issue May 19, 2020
Summary:
Issues like tensorflow#3460, tensorflow#3481, and tensorflow#3592 are all caused by an incompatibility
between certain versions of TensorBoard and the standalone What-If Tool.
This patch adds a check to the diagnosis script to warn accordingly.

Test Plan:
Install `tensorflow==2.1.0 tensorboard-plugin-wit==1.6.0.post2` into a
new virtualenv, and note that TensorBoard fails to start. Then run the
diagnosis script and note that it prints a suggestion with a command
that, when executed, solves the problem.

wchargin-branch: diagnose-broken-wit
caisq pushed a commit that referenced this issue May 27, 2020
Summary:
Issues like #3460, #3481, and #3592 are all caused by an incompatibility
between certain versions of TensorBoard and the standalone What-If Tool.
This patch adds a check to the diagnosis script to warn accordingly.

Test Plan:
Install `tensorflow==2.1.0 tensorboard-plugin-wit==1.6.0.post2` into a
new virtualenv, and note that TensorBoard fails to start. Then run the
diagnosis script and note that it prints a suggestion with a command
that, when executed, solves the problem.

wchargin-branch: diagnose-broken-wit
@ghost
Copy link
Author

ghost commented Dec 2, 2020

Please be so kind to delete this issue for me, thank you in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant