-
Notifications
You must be signed in to change notification settings - Fork 255
Compiler panic while running rls --cli
#1107
Comments
Full trace
|
Works fine for me, which crate do you want to compile? |
Unfortunately I cannot disclose the crate's code. It might be failing to build the dependent This happens 100% on my specific crate but other crates are unaffected. |
nightly-2018-10-20 also unaffected by the crash, but has #1106 |
nightly-2018-10-17 unaffected by the crash, unaffected by #1106 |
Will stick to nightly-2018-10-17 for the time being. |
Took the liberty to create a small project that breaks with this message... https://github.com/lweberk/bug-rls-1107. Its basically a bare bone rocket project with only Environment prep and execution to achieve the error:
Edit: maybe worth adding:
|
Can confirm the earliest nightly version failing in the case of https://github.com/lweberk/bug-rls-1107 is 2018-10-27. Narrowed down to 2018-10-26 being the last working one. |
Still open as for 2018-11-06
|
Still open with rustc 1.32.0-nightly (15d770400 2018-11-06) running on x86_64-unknown-linux-gnu |
I suppose, then, that this is a 1.32 + rls issue, since it was when we moved into the 1.32 series that the issue crept up. |
@jnicholls It was there in rustc 1.31.0-nightly (96064eb 2018-10-28) when I initially reported it. |
After some investigating it turns out #1117 boils down to the same problem and since I left some more context and it's already labeled there, I'll close this as dup and track the underlying bug there. Thanks for the report, I'm looking into this! |
@Xanewok sounds like a plan, cheers! :) |
Crash doesn't happen on normal "cargo build", only when running
rls --cli
on the same crate.UPDATE: Still open with rustc 1.32.0-nightly (15d770400 2018-11-06) running on x86_64-unknown-linux-gnu
RLS basically unusable.
The text was updated successfully, but these errors were encountered: