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
Hi
I am using this extension on WSL without a problem. But, being licenced, our build tools run on a job queue remotely. Which means that is where the source files need to be located. If I connect to a remote, e.g. over SSH, it can't find the language server. As it's not installed there.
I get the error:
[Error - 10:55:10 AM] veribleVerilogLs language server client: couldn't create connection to server.
Launching server using command /home/jm48/.local/bin/verible-verilog-ls failed.
Error: spawn /home/jm48/.local/bin/verible-verilog-ls ENOENT
Same withiout the explicit path, but the .local/bin obviously is in the PATH.
I tried 'accidentally' copying the executable there (we are not supposed to put downloaded executable on this sistem) but that did not work. I tried building the language server there but sadly Verible uses Bazel which is far too new (needs recent JDK) and can't be run on old systems.
There is an option in VSCode to run remote extensions locally, I tried this but that does not work (MS say this feature is something that is limited by the capabilities of the extension)
remote settings file
Hi
I am using this extension on WSL without a problem. But, being licenced, our build tools run on a job queue remotely. Which means that is where the source files need to be located. If I connect to a remote, e.g. over SSH, it can't find the language server. As it's not installed there.
I get the error:
Same withiout the explicit path, but the .local/bin obviously is in the PATH.
I tried 'accidentally' copying the executable there (we are not supposed to put downloaded executable on this sistem) but that did not work. I tried building the language server there but sadly Verible uses Bazel which is far too new (needs recent JDK) and can't be run on old systems.
There is an option in VSCode to run remote extensions locally, I tried this but that does not work (MS say this feature is something that is limited by the capabilities of the extension)
remote settings file
the default is
workspace
rather thanui
If I run the (accidentally, honest!) copied file it does work:
So there is something about the way the LS is started by the extension that is causing the issue.
The text was updated successfully, but these errors were encountered: