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
edit added a further clarification on where it runs
Firstly, thanks so much for this extension. Pluto is great, and running it in VSCode is even better.
Issue as the title suggests, essentially. I've got WSL2 running on a Windows 10 machine on my home network. I can successfully use Remote-SSH to access the OpenSSH server running through to WSL2 and can run Julia files remotely using VSCode. However, when I try to "Open with Pluto.jl" from the file explorer, it hangs at "Loading Pluto". The same notebook opens without errors on the laptop I am using, also through WSL2 on Windows 10, and also will run natively on WSL2 through VSCode on the server machine. It's just the use of SSH that seems to create the issue. I see that the extension has successfully handled SSH, so my first thought is that, if nothing's broken my end, it may just not like SSH'ing into WSL2.
The remote PC's WSL2 distro is Ubuntu 20.04.4 LTS (focal), and has Julia 1.7.3 installed. The laptop is running the same version of Ubuntu, also under WSL2, and has Julia 1.7.2.
I'm not sure where to look for logs that may be useful here?
Hi there,
edit added a further clarification on where it runs
Firstly, thanks so much for this extension. Pluto is great, and running it in VSCode is even better.
Issue as the title suggests, essentially. I've got WSL2 running on a Windows 10 machine on my home network. I can successfully use Remote-SSH to access the OpenSSH server running through to WSL2 and can run Julia files remotely using VSCode. However, when I try to "Open with Pluto.jl" from the file explorer, it hangs at "Loading Pluto". The same notebook opens without errors on the laptop I am using, also through WSL2 on Windows 10, and also will run natively on WSL2 through VSCode on the server machine. It's just the use of SSH that seems to create the issue. I see that the extension has successfully handled SSH, so my first thought is that, if nothing's broken my end, it may just not like SSH'ing into WSL2.
The remote PC's WSL2 distro is Ubuntu 20.04.4 LTS (focal), and has Julia 1.7.3 installed. The laptop is running the same version of Ubuntu, also under WSL2, and has Julia 1.7.2.
I'm not sure where to look for logs that may be useful here?
There is a small chance this issue is related to the next most recent one
Thanks for any help!
The text was updated successfully, but these errors were encountered: