RLS nightly not working

[sophiajt]

There might be an obvious fix, but the RLS isn't working for me as of the most recent nightly.

The spinner spins, but when it stops nothing has occurred, and there are no warnings about the RLS crashing. This is with the latest version of the vs code plugin as well.

I'm on Windows, if that helps.

[sophiajt]

Poked around a bit and seemed to have knocked it out of the bad state. Not sure how I got in it. If I can reliably repro, I'll reopen.

[sophiajt]

Reopening. It seems that you can get it to fix itself if you change the user settings. But regular editing will eventually (especially adding or removing 'extern crate' statements) will get it into a state where it no longer functions.

[71]

@jonathandturner Hey, can you expand on "changing the user settings"? I might have the same problem as you do. Thanks.

[sophiajt]

If I open the user settings and poke lines like:

"rust-client.channel": "nightly"

It seems to make it work for a while.

[71]

Oh, then it appears we have different problems. Mine crashes after a few dozen seconds with no backtrace.

[alexheretic]

Perhaps related to an issue with latest nightly where it outputs to stdout after a compiler panic rust-lang/rust#48816. vscode-jsonrpc is irrecoverably broken by this.

So previously subsequent builds may have worked after a rustc panic, now you'll need to restart your client comms.

[gilescope]

Any news? Apparently RLS nightlies are stopping Rust nightlies.

[gilescope]

Looks like rust-lang/rust#48993 will fix this. Good sluthing!

[mati865]

Any news? Apparently RLS nightlies are stopping Rust nightlies.

Fixed by rust-lang/rust#49014

[alexheretic]

The particular stdout abuse I reproduced is now fixed and available in nightly-2018-03-14. Rustc panics may still happen but the rls->client comms won't be broken, until the next time something prints.

Does this fix this issue @jonathandturner?

[nrc]

Not seen by reporter for a while, presumed fixed.