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
Not connecting to Matlab when connected to a server with matlab using a tunnel
To Reproduce
Steps to reproduce the behavior:
Start a tunnel to a server with Matlab installed
In Matlab configuration, add the result of the remote server's matlabroot
Ask to connect to matlab
See forever MATLAB: Establishing Connection
Expected behavior
I would like to run 1+1 in my remote file with shift+enter in my console, that actually runs in the remote server's matlab
Screenshots
I don't think it is required
Useful Information
OS Version: server Ubuntu, local: macos Sequoia
VS Code Version: 1.93.1
Additional context
No more context, it would be great to have a system to test if local VS Code is able to see remote Matlab. Right now, I edit the .m in the remote machine, and I copy and paste into a remote terminal, where I have a "matlab -nodesktop' opened
The text was updated successfully, but these errors were encountered:
Can you please share the language server logs from your VS Code session. These can be found using the following directions:
Open the Output panel in VS Code (can be opened using Shift+Cmd+U)
In the drop-down, select "MATLAB Language Server"
At the top of the log, there should be a "Log Directory" printed
Please share the log flies from this directory
It would also be helpful if you could provide example steps of how you are setting up the tunnel, including the value you are specifying as the matlabroot.
Describe the bug
Not connecting to Matlab when connected to a server with matlab using a tunnel
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would like to run 1+1 in my remote file with shift+enter in my console, that actually runs in the remote server's matlab
Screenshots
I don't think it is required
Useful Information
Additional context
No more context, it would be great to have a system to test if local VS Code is able to see remote Matlab. Right now, I edit the .m in the remote machine, and I copy and paste into a remote terminal, where I have a "matlab -nodesktop' opened
The text was updated successfully, but these errors were encountered: