Closed jecs closed 7 months ago
Thank you for sharing this info!
Here are a few additional questions which would be helpful:
HTTP_PROXY
, HTTPS_PROXY
, and NO_PROXY
sudo lsof -i -P -n > lsof.txt
lsof.txt
file, find the entry for MATLAB. It should look something like the following:
MATLAB 12345 username 1120u IPv4 123456123 0t0 TCP 127.0.0.1:35737 (LISTEN)
curl -v -k https://127.0.0.1:35737
Of course. Thank you for your reply!
~ % echo $HTTP_PROXY
~ % echo $HTTPS_PROXY
~ % echo $NO_PROXY
The only thing that *might* be interfering is the Falcon content filter that the university/hospital requires on this machine. I have had no issues with it so far.
2. I followed your instructions. I made sure that no instances of MATLAB were running by Force Quitting the zombie instances using System Monitor. I attempted to connect once. I see two instances of MATLAB running now. `lsof` lists a couple of ports that are listed with `(LISTEN)` and do not have established connections. I attach one for the first process and one for the second.
[curl1.txt](https://github.com/mathworks/MATLAB-extension-for-vscode/files/14272827/curl1.txt)
[curl2.txt](https://github.com/mathworks/MATLAB-extension-for-vscode/files/14272828/curl2.txt)
I have the same problem.
Figured it out! It seems that it's the "New Desktop" addon that is preventing VSCode from connecting. Disabling the new desktop resolves the issue. Not ideal for my sensitive eyes, but it's a workaround for now.
Thanks for letting us know! This is a known issue (captured in #24) which we are working to resolve.
Describe the bug VSCode fails to connect to MATLAB, even though it starts a new process every time, as verified on System Monitor.
To Reproduce
Expected behavior I expect a connection to be established and for VSCode to only launch one instance.
Useful Information
Additional context Here are the extension logs: