-
Notifications
You must be signed in to change notification settings - Fork 13
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
Impossible to "ssh-copy-id mila" in the "mila init" process on Windows 11 #63
Labels
windows
Issues related to Windows support
Comments
Hi, I have the same problem. I found one issue may be helpful. #19 |
lebrice
added a commit
to lebrice/milatools
that referenced
this issue
Nov 2, 2023
Fixes mila-iqia#63 Signed-off-by: Fabrice Normandin <[email protected]>
lebrice
added a commit
to lebrice/milatools
that referenced
this issue
Nov 6, 2023
Fixes mila-iqia#63 Signed-off-by: Fabrice Normandin <[email protected]>
lebrice
added a commit
to lebrice/milatools
that referenced
this issue
Nov 8, 2023
Fixes mila-iqia#63 Signed-off-by: Fabrice Normandin <[email protected]>
lebrice
added a commit
that referenced
this issue
Nov 11, 2023
* Dont add ControlMaster ssh entries on Windows Signed-off-by: Fabrice Normandin <[email protected]> * Remove the unused params of _add_ssh_entry Signed-off-by: Fabrice Normandin <[email protected]> * Rebase on Master Signed-off-by: Fabrice Normandin <[email protected]> * Fix isort issues Signed-off-by: Fabrice Normandin <[email protected]> * Fix the `mila init` command on windows Fixes #63 Signed-off-by: Fabrice Normandin <[email protected]> * Fix black formatting errors Signed-off-by: Fabrice Normandin <[email protected]> * Fix the equivalent of ssh-copy-id, now works! Signed-off-by: Fabrice Normandin <[email protected]> * Attempt to fix running `mila code` from WSL Signed-off-by: Fabrice <[email protected]> * Fix whitespace errors and run `code` directly Signed-off-by: Fabrice Normandin <[email protected]> * Set the remote.SSH settings in User Settings Json Signed-off-by: Fabrice Normandin <[email protected]> * Show that VsCode settings are found Signed-off-by: Fabrice Normandin <[email protected]> * Remove the VsCode settings thing for now Signed-off-by: Fabrice Normandin <[email protected]> * Use `here.run` to run the command Signed-off-by: Fabrice <[email protected]> * Skip the hostname checking on Windows machines Signed-off-by: Fabrice <[email protected]> * Fix black formatting issue Signed-off-by: Fabrice Normandin <[email protected]> * Fix missing condition in WSL check Signed-off-by: Fabrice Normandin <[email protected]> * Warn WSL users if `mila init` not done on Windows Signed-off-by: Fabrice Normandin <[email protected]> * Also setup Windows SSH config from WSL Signed-off-by: Fabrice Normandin <[email protected]> * Fix isort issues Signed-off-by: Fabrice Normandin <[email protected]> * Reuse existing fn to setup windows SSH file Signed-off-by: Fabrice Normandin <[email protected]> * Preserve ordering of SSH entries when copying Signed-off-by: Fabrice Normandin <[email protected]> * Copy both public and private key files Signed-off-by: Fabrice Normandin <[email protected]> * Add tests for the Windows SSH setup from WSL Signed-off-by: Fabrice Normandin <[email protected]> * Remove need for pytest-mock dependency Signed-off-by: Fabrice Normandin <[email protected]> * Fix a bug in the added tests Signed-off-by: Fabrice Normandin <[email protected]> * Remove accidentally-added .pre-commit-config.yaml Signed-off-by: Fabrice Normandin <[email protected]> --------- Signed-off-by: Fabrice Normandin <[email protected]> Signed-off-by: Fabrice <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Make sure you can reproduce the issue with the latest version available
What command did you run?
mila init
Then i entered my username on the mila cluster as asked by the command prompt.
Then I answered to the question
Then I answered yes to the question
? You have no public keys. Generate one?
Then I answered yes to the question
? Your public key does not appear be registered on the cluster. Register it? Yes
Then I got the error below.
Describe the bug
In the "mila init process" on my Windows PC, I get stucked at this point, although I upgrade the milatools package.
Screenshots
![image (2)](https://github.com/mila-iqia/milatools/assets/146956184/70576fd4-74a5-4107-be86-3f9b37394750) ![image (1)](https://github.com/mila-iqia/milatools/assets/146956184/cf74d81f-f8c9-42d2-80b6-7d391b383d78) ![image](https://github.com/mila-iqia/milatools/assets/146956184/cd9b4ec8-0ba8-4ceb-bf04-35a7887311fc)Desktop (please complete the following information):
Additional context
I started following Victor Schmidt's guide (https://vsch.notion.site/YAMSS-5471da23464e41d4bad5e3517d273dea#0742904b6e384aba94b29a24b69e7b0e) on my WSL machine. But I decided to try milatools because I am on Windows, which is a problem if I want to open VS Code on a compute node following Victor's guide.
The text was updated successfully, but these errors were encountered: