-
Notifications
You must be signed in to change notification settings - Fork 165
RLS not installed message, but it is installed #461
Comments
I have the same issue, same setup (but on Mojave). |
The check for the RLS is here: https://github.com/rust-lang/rls-vscode/blob/master/src/rustup.ts#L126 If you could debug the extension and find out what |
|
Changing a setting: |
Default should be already set to |
When will the fix be released (on the Marketplace)? |
Fixes rust-lang#461. This should be due to renamed `rls-preview` -> `rls` component for Rust 2018. r? @nrc
this is broken again due to 4af0073 (might be my newness to rust.. looks like I installed a nightly build that doesn't have rls available - ref: https://github.com/rust-lang/rls/blob/master/README.md#error-component-rls-is-unavailable-for-download-nightly) |
Tomorrow's nightlies should have the |
Yes, but the rls-preview component is not available. |
Still getting |
Try installing an older (< 2019-03-23) nightly version. You can check which tools are available in which nightly version here: https://rust-lang-nursery.github.io/rust-toolstate/ |
I am still hitting this with |
I was getting this error too. In my case it turned out to be because I had set a specific nightly as default in rustup ( The documentation for the
So I removed the This behavior is a bit confusing, but there's an open PR (#712) to make the default behavior an explicit setting at least. |
I'm using version 0.4.10 of rls-vscode, and 1.29.1 of VSCode. I have disabled all extensions except rls-vscode. OS is macOS High Sierra.
When opening a rust project in VSCode, I see a message box saying "RLS not installed. Install?" and my only option is to click "Yes." However, I do have the RLS installed, and when I click "Yes", everything works as if the RLS was immediately found, and no extra install step happens.
If I do not click "Yes" on this box, the toolbar spinner stays in the "Starting" state forever.
The log to file feature does not provide any output.
The text was updated successfully, but these errors were encountered: