Skip to content

Conversation

@rushtehrani
Copy link
Contributor

What this PR does:
This allows TensorBoard to be used in Onepanel's JupyterLab Workspaces.

Special notes for your reviewer:
Example usage in JupyterLab:

# Load the TensorBoard notebook extension.
%load_ext tensorboard

# Run TensorBoard within Onepanel's JupyterLab
%tensorboard --logdir <path-to-logs> --path_prefix /tensorboard

Checklist

Please check if applies

  • I have added/updated relevant unit tests
  • I have added/updated relevant documentation

Required

  • I accept to release these changes under the Apache 2.0 License

@rushtehrani rushtehrani added this to the v0.15.0 milestone Oct 31, 2020
@rushtehrani rushtehrani changed the title fix: Set TENSORBOARD_PROXY_URL so it can be used in JupyterLab [DO NOT MERGE] fix: Set TENSORBOARD_PROXY_URL so it can be used in JupyterLab Oct 31, 2020
@rushtehrani rushtehrani changed the title [DO NOT MERGE] fix: Set TENSORBOARD_PROXY_URL so it can be used in JupyterLab fix: Set TENSORBOARD_PROXY_URL so it can be used in JupyterLab Nov 1, 2020
@rushtehrani rushtehrani changed the title fix: Set TENSORBOARD_PROXY_URL so it can be used in JupyterLab fix: Set TENSORBOARD_PROXY_URL so TensorBoard can easily be used in JupyterLab Nov 2, 2020
// These hooks will attempt to persist conda, pip, and jupyterlab extensions between pause and shut-down.
func Up20201031165106(tx *sql.Tx) error {
// This code is executed when the migration is applied.
return updateWorkspaceTemplateManifest("20201031165106_jupyterlab.yaml", jupyterLabTemplateName)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aleksandrmelnikov @Vafilor I think for the YAML name, we should have the timestamp first so things are ordered in the IDE accordingly. Thoughts?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rushtehrani Good point, yeah, let's do that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed

// Down20201031165106 removes the lifecycle hooks from the template.
func Down20201031165106(tx *sql.Tx) error {
// This code is executed when the migration is rolled back.
return updateWorkspaceTemplateManifest("20201028145442_jupyterlab.yaml", jupyterLabTemplateName)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aleksandrmelnikov @Vafilor When doing down migrations, I'm proposing we use the previous YAML here. Thoughts, issues?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's fine.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure

@rushtehrani rushtehrani merged commit 6c1f522 into onepanelio:master Nov 2, 2020
@rushtehrani rushtehrani deleted the fix/tensorboard branch November 2, 2020 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants