Skip to content
This repository was archived by the owner on Dec 8, 2020. It is now read-only.

No Lints in RLS mode #185

Closed
rfurlan opened this issue Apr 19, 2017 · 5 comments
Closed

No Lints in RLS mode #185

rfurlan opened this issue Apr 19, 2017 · 5 comments

Comments

@rfurlan
Copy link

rfurlan commented Apr 19, 2017

Version of VSCode: 1.11.2
Version of the extension: 0.3.11
OS: Windows 10

Description:

No Lints in RLS mode, appears to be an issue with the top-level workspace cargo.toml.

Output of the "Rust Language Server" channel:

INFO:rls_analysis: find_all_refs: 0.000029234s
DEBUG:rls::server: response: "Content-Length: 36\r\n\r\n{\"jsonrpc\":\"2.0\",\"id\":5,\"result\":[]}"
DEBUG:rls::server: response: "Content-Length: 72\r\n\r\n{\"jsonrpc\":\"2.0\",\"method\":\"rustDocument/diagnosticsBegin\",\"params\":null}"
DEBUG:rls::actions: build "c:\\Development\\cyberverse"
DEBUG:rls::server: response: "Content-Length: 36\r\n\r\n{\"jsonrpc\":\"2.0\",\"id\":6,\"result\":[]}"
thread '<unnamed>' panicked at 'could not run cargo: manifest path `c:\Development\cyberverse\Cargo.toml` is a virtual manifest, but this command requires running against an actual package in this workspace', src\libcore\result.rs:859
stack backtrace:
   0: <std::time::SystemTimeError as core::fmt::Display>::fmt
   1: std::panicking::Location::line
   2: std::panicking::Location::line
   3: std::panicking::rust_panic_with_hook
   4: std::panicking::begin_panic_fmt
   5: std::panicking::begin_panic_fmt
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: <unknown>
   9: <unknown>
  10: _rust_maybe_catch_panic
  11: <unknown>
  12: std::sys::imp::thread::Thread::new
  13: BaseThreadInitThunk
INFO:rls::build: cargo stdout 
INFO:rls::build: cargo stderr 
DEBUG:rls::server: response: "Content-Length: 70\r\n\r\n{\"jsonrpc\":\"2.0\",\"method\":\"rustDocument/diagnosticsEnd\",\"params\":null}"
DEBUG:rls::server: response: "Content-Length: 62\r\n\r\n{\"jsonrpc\":\"2.0\",\"id\":7,\"result\":{\"contents\":[],\"range\":null}}"
DEBUG:rls::server: response: "Content-Length: 62\r\n\r\n{\"jsonrpc\":\"2.0\",\"id\":8,\"result\":{\"contents\":[],\"range\":null}}"
DEBUG:rls::server: response: "Content-Length: 62\r\n\r\n{\"jsonrpc\":\"2.0\",\"id\":9,\"result\":{\"contents\":[],\"range\":null}}"
DEBUG:rls::server: response: "Content-Length: 63\r\n\r\n{\"jsonrpc\":\"2.0\",\"id\":10,\"result\":{\"contents\":[],\"range\":null}}"
DEBUG:rls::server: response: "Content-Length: 63\r\n\r\n{\"jsonrpc\":\"2.0\",\"id\":11,\"result\":{\"contents\":[],\"range\":null}}"
DEBUG:rls::server: response: "Content-Length: 63\r\n\r\n{\"jsonrpc\":\"2.0\",\"id\":12,\"result\":{\"contents\":[],\"range\":null}}"
@KalitaAlexey
Copy link
Member

@jonathanturner @nrc,
I suppose it belongs to your repository, right?

@rfurlan
Copy link
Author

rfurlan commented Apr 19, 2017

Related: rust-lang/rls#263

@KalitaAlexey
Copy link
Member

Good to know.
Thank you.

@rfurlan
Copy link
Author

rfurlan commented Apr 19, 2017

Actually, I am the one who should be thanking you :)

@KalitaAlexey
Copy link
Member

I am closing this issue since we think it is not the extension's issue.
If you find out that it is, re-open this issue.

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

No branches or pull requests

2 participants