Nick Groszewski

Hey @k82cn, just wanted to circle back and see if there has been any shift in prioritization on this?

Would you mind running `tensorboard --inspect --logdir ` and providing the results?

Is this still an issue now that googlecolab/colabtools#3990 has been resolved?

You would need to add your own auth layer in front of any locally hosted version of TensorBoard, which would be specific to your particular auth provider. The TB HTML...

How are you running TensorBoard in this situation? Are the log files created in the same directory? Are all steps recomputed in the new file, or are only newer steps...

Have you tried specifying [--reload_multifile](https://github.com/tensorflow/tensorboard?tab=readme-ov-file#tensorboard-is-showing-only-some-of-my-data-or-isnt-properly-updating)?

Can you please provide the output of `tensorboard --inspect --logdir ` as well as the result of `diagnose_tensorboard.py` as specified in the [issue template](https://github.com/tensorflow/tensorboard/issues/new?assignees=&labels=&projects=&template=bug_report.md&title=)?

The output of `tensorboard --inspect --logdir` looks like you actually passed it `tensorboard --inspect --event_file ` instead. There should not be an error, I would expect either `No event files...

Would you mind running with `--purge_orphaned_data=False` set and see if that helps? It doesn't seem like your situation is the same, but this may help us to debug ([doc link](https://github.com/tensorflow/tensorboard/blob/master/README.md#how-should-i-handle-tensorflow-restarts)).

Are you able to copy the log directory locally and confirm that things work as expect? Would like to rule out whether this is something internal to TB or isolated...