Closed amansouri3476 closed 1 year ago
I'm going to try to reproduce the problem later but in the meantime can you try answering "No" at the prompt ? The '*.server.mila.quebec' entry in ~/.ssh/config is too general and should exclude login.server.mila.quebec. Fix this?
If that doesn't work, you can also manually remove or comment out that existing entry in ~/.ssh/config
.
Answering "No" fixes the problem actually. I'm sorry I didn't try it myself, I thought that fix is a necessary step. I can now do ssh mila-cpu
and mila code path/to/code
to open a vscode window.
Thanks so much for the new features of milatools!
No problem, it makes sense that you thought it was necessary. And what you reported appears to be an actual bug, so I'll keep this open until we can fix it.
The bug should be fixed in 0.0.18.
I tried to update milatools to be able to do
ssh mila-cpu
. I followed the instructions that were put in the slack channel. First I did:pip install -U milatools
and got the following output:Then I tried running
mila init
and got the following error:I tried
pip install milatools --upgrade
but got the following:Running
mila init
for another time gave the same error and it appears that issue persists, so I opened this issue.Desktop:
Thanks a lot for this new feature. I can't wait to use it once this issue is resolved!