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
Describe the bug
I'm trying to using vscode locally and connect and run notebook on the remote databricks server through the vscode databricks extension.
i think this is related to notebook server itself instead of the databricks server, i.e. whenver you spin up a jupyter notebook server, it asks you to create password, i imagine it's this passowrd that is preventing me to connect.
just want to confirm if thats the case (so i need to reach out to admin)
how does databricks setup notebook server actually? is it one notebook server per databricks user or everyones notebook spins up from under the same server (so everyone shares the same password as well)?
To Reproduce
Steps to reproduce the behavior:
I synced to the server in vscode, although when i try to execute the cell, id like to use python env/exec from the server (instead of my local python thats different from the servers), but it prompts me password.
Screenshots
If applicable, add screenshots to help explain your problem.
System information:
Databricks Extension Version
1.3.0
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm trying to using vscode locally and connect and run notebook on the remote databricks server through the vscode databricks extension.
i think this is related to notebook server itself instead of the databricks server, i.e. whenver you spin up a jupyter notebook server, it asks you to create password, i imagine it's this passowrd that is preventing me to connect.
To Reproduce
Steps to reproduce the behavior:
I synced to the server in vscode, although when i try to execute the cell, id like to use python env/exec from the server (instead of my local python thats different from the servers), but it prompts me password.
Screenshots
If applicable, add screenshots to help explain your problem.
System information:
1.3.0
The text was updated successfully, but these errors were encountered: