You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to add a feature when gs:// or s3:// log_dir can be specified for Tensorboard to start? Assuming the environment is already authenticated to the GCP or AWS.
I'm running job in Google Cloud ML Engine and logs are in a GCS bucket. Also using JupyterLab inside a container on the cloud instances where this can be added too if supported by this package. chesterli29/jupyterlab_tensorboard#9 (comment)
cc @chaoleili
The text was updated successfully, but these errors were encountered:
While this is still not working, you can start tensorboard from the Cloud Shell, and preview on port 6006 (or whatever port you use for running tensorboard).
However, it'd be nice to open tensorboard from the jupyterlab without this workaround.
Would it be possible to add a feature when gs:// or s3:// log_dir can be specified for Tensorboard to start? Assuming the environment is already authenticated to the GCP or AWS.
I'm running job in Google Cloud ML Engine and logs are in a GCS bucket. Also using JupyterLab inside a container on the cloud instances where this can be added too if supported by this package. chesterli29/jupyterlab_tensorboard#9 (comment)
cc @chaoleili
The text was updated successfully, but these errors were encountered: