-
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
TensorBoard: gracefully handle deleted event files #2634
Comments
Hi @makslevental, perhaps I am missing few things here but what exactly is an issue? AFAICT, it is gracefully handling the deleted event files by printing warning about the deleted runs and it prints something like below.
|
i get no such "deleting accumulator" print and the run still stays up in the dashboard. |
Raised exception causes the application "Reloader" thread exited, so that the graph won't be updated anymore.
This seems like a bug, what I expect behavior would be:
FYI, full callstack:
|
so do you already have some plan to fix this issue ? If needed I could describe the issue and proposal fix with more details. |
Sorry for being unresponsive. Somehow, this issue got drop out of my plate and just found it again thanks to @thincal. I think I can benefit from better repro case. What I am doing right now. virtualenv 1_15
source 1_15/bin/activate
pip install tensorflow==1.15
pip uninstall tensorboard
pip install tb-nightly==1.15.0a20190911
# In TensorBoard repo
bazel run tensorboard/plugins/scalar:scalars_demo
# above creates demo scalars data in /tmp/scalars_demo
# Outside of the repo directory
tensorboard --logdir /tmp/scalars_demo
# On another terminal
rm -rf "/tmp/scalars_demo/temperature:t0=270,tA=270,kH=0.001"
# Notice on the terminal running TensorBoard, it prints something like below:
W1107 08:53:01.393033 140467294635776 plugin_event_multiplexer.py:250] Deleting accumulator 'temperature:t0=270,tA=270,kH=0.001'
# Refreshing the TensorBoard UI removes the run from the left selector and from our charts I have never tried to remove an event file from a folder but that should not remove the run from the run selector on the left. @thincal, when you post more complete reproducible case, please attach version of TensorBoard you are using too. |
@stephanwlee Sorry for the late reply, here is the detailed info FYI: Case: deleting the folder will result in the multiplexer Reloader process crashHow to repoENV: tensorboard 1.14, tensorboard 2.0.0 STEPS:
Detailed Error Info
Both exception is not gracefully handled and will crash the Detailed callback for the deleting folder:
Proposal fix
|
@thincal I really cannot reproduce your steps.
Deleting the folder
Can you provide us with more details by following the steps here? Thanks.
|
@stephanwlee one important thing forget to mention, I just run the tensorboard without tensorflow installed, you could try it again. |
Any plan or thoughts with this issue ? Thanks @nfelt |
as far as i can tell this is exactly the same as this issue tensorflow/tensorflow#3267
if i delete files from the logdir while tensorboard is running i get things like
i'm using
tb-nightly==1.15.0a20190911
through pytorch.i'm not sure when reaping is supposed to happen e.g. as in tensorflow/tensorflow#3267 (comment)
or how to manually force
The text was updated successfully, but these errors were encountered: