Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with language servers and vscode/remote/ssh #451

Open
the-moog opened this issue Oct 23, 2023 · 0 comments
Open

Issue with language servers and vscode/remote/ssh #451

the-moog opened this issue Oct 23, 2023 · 0 comments

Comments

@the-moog
Copy link

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

    "remote.extensionKind": {
        "mshr-h.veriloghdl": [ "ui" ],

the default is workspace rather than ui

If I run the (accidentally, honest!) copied file it does work:

bash-4.2$ ./verible-verilog-ls Verible Verilog Language Server built at v0.0-3424-g66c8c26f

So there is something about the way the LS is started by the extension that is causing the issue.

  • Can the extension be made to support the run locally option?
  • Is there a way to increase the debug output from this extension?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant