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

why unkonwn rls configuration use_crate_blacklist #639

Closed
theone-pang opened this issue Aug 7, 2019 · 14 comments · Fixed by #678
Closed

why unkonwn rls configuration use_crate_blacklist #639

theone-pang opened this issue Aug 7, 2019 · 14 comments · Fixed by #678
Milestone
0.6.2

Comments

@theone-pang
Copy link

open project show "unkonwn rls configuration use_crate_blacklist " tip evry time,why?
@greensirius
Copy link

I have the same issues here on my vscode, my current rls is 1.38.0

@mati865
Copy link

mati865 commented Aug 8, 2019

It's because of rust-lang/rls#1509
cc @Xanewok

@Xanewok
Copy link
Member

Xanewok commented Aug 8, 2019

Yup, will push a new extension version today.

Sorry for the inconvenience.

@arlyon
Copy link

arlyon commented Aug 11, 2019 •
edited
Loading

Any update on this? Still getting this issue, even on master.

@arlyon arlyon mentioned this issue Aug 11, 2019
Closed
@Xanewok Xanewok mentioned this issue Aug 11, 2019
Merged
@Xanewok
Copy link
Member

Xanewok commented Aug 11, 2019

Sorry for the delay! I'll publish a version when rust-lang/rust#63472 is merged upstream (it looks like it's going to be tomorrow) - with this, the RLS will be able to emit a user friendly error whenever use_crate_backlist is still specified.

bors pushed a commit to rust-lang/rust that referenced this issue Aug 11, 2019
@Xanewok
Update RLS
c8a2855 
This update includes the ability to warn on deprecated config keys.
It's important to be able to warn the user whenever they're using
an old configuration rather than giving them a cryptic "unknown
configuration error"

cc rust-lang/vscode-rust#639

Since we removed a config value in the current nightly, it'd be
very good if this change can make also make it before cutting the
next release.
bors added a commit to rust-lang/rust that referenced this issue Aug 11, 2019
@bors
Auto merge of #63472 - Xanewok:update-rls, r=Mark-Simulacrum
899efd5 
Update RLS

This update includes the ability to warn on deprecated config keys.
It's important to be able to warn the user whenever they're using
an old configuration rather than giving them a cryptic "unknown
configuration error"

cc rust-lang/vscode-rust#639

Since we removed a config value in the current nightly, it'd be
very good if this change can make also make it before cutting the
next release.
@zuobaoquan
Copy link

Workaround for VSCode: add "rust.use_crate_blacklist": false to settings.json and restart the editor.

@mati865
Copy link

mati865 commented Aug 12, 2019 •
edited
Loading

It's fixed in upcoming nightly release.

@Xanewok Xanewok added this to the 0.5.2 milestone Aug 12, 2019
@Xanewok Xanewok mentioned this issue Aug 12, 2019
Merged
@billylindeman billylindeman mentioned this issue Aug 14, 2019
Closed
@Xanewok
Copy link
Member

Xanewok commented Sep 7, 2019

This was fixed in the newest RLS edition and a new version of the extension was published, so this shouldn't pop up anymore.

@Xanewok Xanewok closed this as completed Sep 7, 2019
@stefanos82
Copy link

Nope, still the same issue, even with 0.6.3

image
P.S.: I've just started learning Rust and installed this extension; it's the very first message I got...nice welcoming 🤣

@mati865
Copy link

mati865 commented Sep 7, 2019

New RLS wasn't yet merged into rust.

@stefanos82
Copy link

This was fixed in the newest RLS edition and a new version of the extension was published, so this shouldn't pop up anymore.

I based my reply on this quote.

@dashed
Copy link

dashed commented Oct 13, 2019

@Xanewok For some reason, I'm receiving this warning for rust projects. I'm using v0.6.3 of rls-vscode 😕

@Xanewok Xanewok mentioned this issue Oct 14, 2019
Merged
@Xanewok
Copy link
Member

Xanewok commented Oct 15, 2019

Please update the extension to the 0.7 version, the Rust toolchain to 1.38 and let me know if the problem still persists, thanks!

@stefanos82
Copy link

stefanos82 commented Oct 16, 2019 •
edited
Loading

The issue remains the same with a slightly different message this time:
image

To fix this problematic behavior you can try a simpler approach: close the currently folder, open the terminal with Ctrl+j or with Ctrl+<Backtick> and find the location of the folder you want to load, and that would be it.

An actual example:

cd ~/code/rust/generic/
vscode .

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.6.2
Development

Successfully merging a pull request may close this issue.

Remove deprecated "rust.use_crate_blacklist" configuration entry Xanewok/rls-vscode
8 participants
@dashed @zuobaoquan @mati865 @stefanos82 @Xanewok @arlyon @theone-pang @greensirius