-
Notifications
You must be signed in to change notification settings - Fork 675
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
Could not sync with existing tensorboard event files #1051
Comments
Hi there, thanks for letting us know about this issue. We'd like to fix syncing problems in the new version of our client, and I'll check with my colleague @raubitsj to see if this case is supported. We're working on a new beta of the Weights & Biases client that improves support for environments like Windows. Would you be interested in giving it a try?
Message us in the wandb-cling channel— we’d love to hear any questions or feedback. |
I also have this problem. My TensorBoard event files were created with PyTorch. I am on Linux. Manjaro Linux 20.0.3 Lysia
|
@vincentwen1995 maybe the discussion in wandb/client-ng#23 (comment) could clarify some things to you. |
Hi @vincentwen1995 I believe this issue is fixed in the latest version of our library, 0.10.0. Could you please try it and reopen the issue if it's still not working? |
Sure, thank you! |
""Could not sync with existing tensorboard event files #1051"" |
wandb --version && python --version && uname
Description
Describe what you were trying to get done.
Tell us what happened, what went wrong, and what you expected to happen.
I am using Anaconda to manage my Python environment and I installed required dependencies for wandb and also pytorch >1.5.0 and tensorboard = 2.2.1. I followed the instructions to log in and sync using the command line interface, but first it requires me to install tensorflow (according to the documentation it should not be a hard requirement) which I did, but then when I tried to sync, it returns an internal error.
What I Did
The text was updated successfully, but these errors were encountered: