rerz

Same thing happening to me. ``` {"message":"expected value, found module `internals::cpu::cpu_impl`","code":{"code":"E0423","explanation":"\nA `struct` variant name was used like a function name.\n\nErroneous code example:\n\n```compile_fail,E0423\nstruct Foo { a: bool };\n\nlet f = Foo();\n//...

@KalitaAlexey How would I access the log? (Win 10) edit: Should have read the template. The logging doesn't change after the server crashes. ``` DEBUG: Rustup: updateToolchains: this.toolchains=[{"channel":"nightly","host":"x86_64-pc-windows-msvc","isDefault":true}] DEBUG: Rustup:...

I'm on Win 10, used `SET RUST_BACKTRACE=1` (Also tried `SET -name RUST_BACKTRACE -value 1`) No output in the powershell I used to start vscode, output in vscode does not seem...

Gonna try on my laptop with arch to see if it's a Windows only issue. Will update if I find something.

Backtrace after crash with `RUST_BACKTRACE=1` ``` thread '' panicked at 'RUST_SRC_PATH is set: NotPresent', /checkout/src/libcore/result.rs:860 note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. stack backtrace: 0:...

I did that right after I read the backtrace, it appears to have fixed the crashing on arch. But on Windows it says `info: component 'rust-src' is up to date`...

Okay I guess that was placebo, it still crashes.

Managed to make it crash again on Arch. ``` thread '' panicked at 'begin

I think removing the components and adding them again through the plugin might have helped. No crashes so far but I don't really have enough time to tets it right...

Followed the same steps on Win 10, still crashing. I assume it didn't "really" work on Arch then either and I was just lucky.