thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value'

[Doaxan]

Version of VSCode: 1.10.1
Version of the extension: 0.3.10
OS: Fedora 25 x86_64

Description:
Sometimes rls dont work and i get:

thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', /checkout/src/libcore/option.rs:323
note: Run with `RUST_BACKTRACE=1` for a backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', /checkout/src/libcore/result.rs:860
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', /checkout/src/libcore/result.rs:860

Output of the "Rust logging" channel:

DEBUG: Language Client Manager: start

settings.json:

    "rust.rls": {
        "revealOutputChannelOn": "never",
        "executable": "rustup",
        "args": ["run", "nightly", "rls"]
    }

rustup:

rustc 1.17.0-nightly (b1e31766d 2017-03-03)

[KalitaAlexey]

@Doaxan,
Next version will include #104
Now you have no choice to restart RLS.
RLS panicking is bad.
You should open an issue in https://github.com/rust-lang-nursery/rls/issues

[FaultyRAM]

This appears to be a duplicate of rust-lang/cargo#3819

[KalitaAlexey]

I suppose it is fixed now.