Skip to content
This repository was archived by the owner on Nov 18, 2022. It is now read-only.

Unknown RLS configuration. #608

Closed
Nucl3arSn3k opened this issue Jun 22, 2019 · 11 comments
Closed

Unknown RLS configuration. #608

Nucl3arSn3k opened this issue Jun 22, 2019 · 11 comments
Labels

Comments

@Nucl3arSn3k
Copy link

Nucl3arSn3k commented Jun 22, 2019

When I open a .rs file in VScode a alert pops up that says

Unknown RLS configuration: mode ,rls ,rust_lang_src_path ,rustup

I am currently using the nightly toolchain.
How can I fix this?

@Xanewok
Copy link
Member

Xanewok commented Jun 23, 2019

Check if you have defined "rust.XYZ" settings (Ctrl + ,) where XYZ is in mode, rls and the rest from the above.

It's possible that you set it for https://github.com/editor-rs/vscode-rust which is a different extension.

@Nucl3arSn3k
Copy link
Author

I have not defined my "rust.XYZ" settings. How would I set it up for this extension?

@Xanewok
Copy link
Member

Xanewok commented Jun 27, 2019

I'd say the default settings are pretty good, you can consult https://github.com/rust-lang/rls-vscode/blob/8d870000cbf959457dbcf1f9e20e670bd6f798df/package.json#L146-L397
to see which options are available.

Can you link your VSCode settings (found via Ctrl + , and clicking the {} (Open Settings (JSON)) in the top-right corner) here?

@Nucl3arSn3k
Copy link
Author

Here you go.

@Xanewok
Copy link
Member

Xanewok commented Jun 28, 2019

As you can see, these:

    "rust.rustLangSrcPath": "C:\\Users\\Kestor Brown\\.rustup",
    "rust.rls": {
        "executable": "rustup",
        "args": [
            "run",
            "nightly",
            "rls"
        ],
        "env": {
            "RUST_LOG": "rls=debug"
        }
    },
    "rust.rustup": {
        "toolchain": "nightly-x86_64-pc-windows-msvc"
    },
"rust.mode": "rls",

are set but all the "rust.*" are passed to the RLS which does not understand them (look up the linked supported settings, these are not on the list).

I personally use these:

"rust-client.channel": "nightly", // Use Rust nightly channel
"rust.clippy_preference": "on", // Always run Clippy lints
"rust.unstable_features": true, // Conditionally enable range formatting, not enabled by default
"rust.all_targets": false, // Don't pass `-all` to `cargo check`, it often takes too much time

@Nucl3arSn3k
Copy link
Author

Ok. thanks

@brainstorm
Copy link

Unknown RLS configuration: crate_blacklist

settings (Ctrl + ,) and search crate_blacklist, rest can fix it

No it doesn't. I just tried to reset via settings and the message keeps appearing after restarting VSCode:

Skärmavbild 2019-09-23 kl  12 29 55

@dasoncheng
Copy link

@brainstorm
look rls-vscode

Short-term solution would be to wait a couple of days for the stable 1.38 release and prune the deprecated config entirely for now.

@brainstorm
Copy link

@dasoncheng I'm actually on insiders edition 1.39.0... so that update didn't work for me :/

Skärmavbild 2019-09-23 kl  21 45 14

@jice-nospam
Copy link

jice-nospam commented Sep 23, 2019

I've had the same message for a few weeks.
Unknown RLS configuration: crate_blacklist
I have no rust.crate_blacklist setting defined, in user, workspace or project configuration. Reinstalling the rls extension doesn't fix it and this error seems to block the RLS compilation. Is there some hidden system-level setting containing this parameter ?

[edit] using stable rust 1.37.0 and rls 0.6.3

@vuldin
Copy link

vuldin commented Sep 23, 2019

The current open ticket for this issue seems to be here: #656

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants