Sync tensorboard stops working in upgrade from 0.9.7 to 0.10.2
See original GitHub issueI had been using sync_tensorboard with the Tensorflow Object Detection API (tensorflow==1.15.2
), but when upgrading to version 0.10.2
metrics are no longer logged to the wandb dashboard.
I have confirmed when downgrading to 0.9.7
the logging begins working again
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:15 (5 by maintainers)
Top Results From Across the Web
Sync tensorboard stops working in upgrade from 0.9.7 to 0.10.2
I had been using sync_tensorboard with the Tensorflow Object Detection API (tensorflow==1.15.2), but when upgrading to version 0.10.2 ...
Read more >Changelog - neptune.ai documentation
Neptune no longer hangs indefinitely if the synchronization thread has stopped when wait() is called. The process also finishes faster when you call...
Read more >Bug listing with status RESOLVED with resolution TEST ...
Bug:233 - "Emacs segfaults when merged through the sandbox." status:RESOLVED resolution:TEST-REQUEST severity:critical · Bug:3888 - "yenta_socket module not ...
Read more >Software Packages in "bionic", Subsection python - Ubuntu
X; python-comedilib (0.10.2-4build7) [universe]: Python wrapper for Comedilib ... python-dnslib (0.9.7+hg20170303-1) [universe]: Module to encode/decode DNS ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@TusharNimbhorkar we just made a branch that addresses support for tboardx, it will go out with in the next release. You can use it now but installing wandb with:
@koulanurag, This is fixed now and will be in the next release: 0.10.3. If you want to try it now use:
@ecatkins, we are still looking into your issue as I believe it is different but the fixes we did might address your problem if you were writing your tensorboard log to cloud storage (s3).