Skip to content
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

Azure docs for using remote jupyter should be more descriptive #8643

Closed
rchiodo opened this issue Jan 5, 2022 · 4 comments
Closed

Azure docs for using remote jupyter should be more descriptive #8643

rchiodo opened this issue Jan 5, 2022 · 4 comments
Assignees
Labels
debt Code quality issues documentation notebook-remote Applies to remote Jupyter Servers

Comments

@rchiodo
Copy link
Contributor

rchiodo commented Jan 5, 2022

https://docs.microsoft.com/en-us/azure/machine-learning/how-to-set-up-vs-code-remote?tabs=studio

Customers aren't sure why remote doesn't sync files automatically (basically this issue here: #1601)

@rchiodo rchiodo added the bug Issue identified by VS Code Team member as probable bug label Jan 5, 2022
@rchiodo
Copy link
Contributor Author

rchiodo commented Jan 5, 2022

We could indicate the files aren't on the remote machine (with a diagram explaining how the server is different from where VS code is running) and then offer some suggestions on how to get them there?

@alfredodeza
Copy link

This issue captures exactly the kind of problem that a beginner or newcomer to using a remote compute option would encounter.
My initial perception on this was that the integration works so well (kudos to the team!) that I naively thought that the files would be synced to the remote compute instance as well.

Concretely, I think that the docs should accomplish these two items:

  1. Highlight (caution/warn/note) the fact that local files aren't immediately available in the remote compute
  2. Mention some options that might work when needing to work with files in the remote. For example, cloning the repo in the remote, or enabling SSH and copying files back/forth

@greazer greazer added documentation notebook-remote Applies to remote Jupyter Servers debt Code quality issues and removed bug Issue identified by VS Code Team member as probable bug needs-triage labels Jan 6, 2022
@greazer
Copy link
Member

greazer commented Jan 6, 2022

Probably makes sense to consolidate the docs on setting this stuff up in one place. Whether we do something to automatically copy workspace files to a remote machine is something we need to discuss. That's the topic of #1601

@greazer greazer added this to the January 2022 milestone Jan 6, 2022
@greazer greazer self-assigned this Jan 6, 2022
@greazer greazer removed this from the February 2022 milestone Feb 24, 2022
@DonJayamanne
Copy link
Contributor

@sevillal Perhaps you might want to take a look into this.
Closing as this isn't related to Jupyter extension.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debt Code quality issues documentation notebook-remote Applies to remote Jupyter Servers
Projects
None yet
Development

No branches or pull requests

5 participants