RLS Cannot be started.

[neildanson]

As of 19/1/2018 (maybe earlier):

Extension says no rls installed, do I want to install. This is strange as rls is installed (via rustup) in cargo bin.

Couldn't start client Rust Language Server
ErrorCould not install RLS component (rls)

VSCode:
Version 1.19.2
Commit 490ef761b76b3f3b3832eff7a588aac891e5fe80
Date 2018-01-10T15:55:03.538Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

Rust installed via rustup -

toolchains installed:

stable-x86_64-pc-windows-gnu
stable-x86_64-pc-windows-msvc
beta-x86_64-pc-windows-msvc
nightly-x86_64-pc-windows-gnu
nightly-x86_64-pc-windows-msvc (default)

Uninstalled the plugin and reinstalling has no effect. Nothing about Rust or RLS in logs.

Not sure exactly what is wrong or how to diagnose more.

[Xanewok]

What's your rustc --version and Rust (rls) extension version?

[neildanson]

rustc 1.25.0-nightly (15a1e2844 2018-01-20)

typing

rls --version

results in
error: toolchain 'nightly-x86_64-pc-windows-msvc' does not have the binary rls.exe

Even though I run it from the folder rls is installed in (.cargo/bin)

[neildanson]

Vs Code plugin version Is 0.3.2

[Xanewok]

You’re saying that RLS is installed via rustup - what does ‚rustup component add rls-preview’ say? The component changed its name some time ago, maybe you have the old component installed?

…

On Sun, 21 Jan 2018 at 17:27, Neil Danson ***@***.***> wrote: Vs Code plugin version Is 0.3.2 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#237 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC8y3UI7UNfECwqqOOZT2yLx9BexQLuuks5tM2VagaJpZM4Rl0bP> .

[neildanson]

It says

info: component 'rls-preview' for target 'x86_64-pc-windows-msvc' is up to date

[neildanson]

I uninstalled all gnu toolchains so that it was clearer what Rust (rls) would be using

Now I get

"The Rust Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted."

[Xanewok]

Hm, that's weird. Would you mind setting a RUST_LOG env var to something like rls=trace,rls_analysis=error and then rerun VSCode? It should give more info about what RLS does and why it's crashing, the err output should be under Output > Rust Language Server window.

[garretmh]

I'm on Windows and having this issue. RLS itself seems to be fine, but the VS Code extension isn't detecting it. Setting those environment variables doesn't seem to have added anything to the output log.

The specific order of events is:

1. Start VS Code
2. "Info: RLS is not installed. Install?"
3. If yes, "Error: Could not install RLS component (rls-preview)"
4. "Error: Couldn't start client Rust Language Server"
5. Output (Rust Language): [Error - 4:48:59 PM] Starting client failed

[jbdutton]

I was experiencing this issue as well. For what it's worth, when looking in my settings rust-client.channel was defaulted to nightly. Switching it to stable fixed the issue.

(In fact, setting RUST_LOG=rls=trace,rls_analysis=error did nothing for me either, the output panel still read "Starting client failed." Only after switching to stable did the trace output appear.)

[garretmh]

Setting "rust-client.channel": "stable" in VS Code user settings worked for me too. Thanks!

[smackysnacks]

Perhaps rls-vscode should handle this the same way the atom plugin does: finding the latest dated channel release with RLS and installing that for them (taken from rust-lang/rls#677 (comment)).

[photex]

I'm on windows, getting the same error even after setting the "rust-client.channel" to stable. No output at all from the extension that I can find.

[neildanson]

Changing to stable worked for me.

[photex]

Sorry, the problem isn't that RLS can't be installed, it's that every time I run Code it says that "Info: RLS is not installed. Install?", if I don't press 'yes' then it says RLS can't be started. If I do press 'yes' then it toils away in the background for a while and after this RLS is available.