Rustup no longer detected

[sophiajt]

Version of VSCode: 1.12.2
Version of the extension: 0.3.14
OS: Mac

Description: Rustup is no longer detected with the most recent VSCode

Output of the "Rust logging" channel:

DEBUG: handleMissingRls: Rust is either not installed or installed not via Rustup
DEBUG: Configuration: updatePathToRacer: findRacerPathSpecifiedByUser: path=undefined
DEBUG: Configuration: updatePathToRacer: findDefaultRacerPath: foundPath=undefined
DEBUG: Legacy Mode Manager: MissingToolsInstallator: getMissingTools(): pathDirectories=["/usr/bin","/bin","/usr/sbin","/sbin"]
DEBUG: Legacy Mode Manager: MissingToolsInstallator: getMissingTools(): tools={"rustfmt":"rustfmt","rustsym":"rustsym"}
DEBUG: Legacy Mode Manager: MissingToolsInstallator: getMissingTools(): this.missingTools = ["racer","rustfmt","rustsym"]

[AndreasHassing]

@jonathandturner I'm using the same version numbers but have no problems.

At a glance, it seems that your pathDirectories variable isn't set appropriately. Shouldn't $PATH contain ~/.cargo/bin for Rust to work in general?

[KalitaAlexey]

@jonathandturner, @AndreasHassing rustc should be available. Since rustc is in ~/.cargo/bin, then the directory should be in PATH.
@jonathandturner, I don't think it was detected before.

[dcbishop]

I had a similar issue. I think it's because I'm using zsh so my path is set in zshrc instead of .bash_profile or whatever, I'm fairly new to vscode so I'm not sure how it grabs things. I solved it by including the path to the executable.

    "rust.rls": {
            "executable": "~/.cargo/bin/rustup",
            "args": ["run", "nightly", "rls"],
    },

[sophiajt]

@AndreasHassing - ah, that might be it. I looked through the docs but didn't see that step. Guessing other people might hit it, too.

[sophiajt]

Looking at my $PATH, it's definitely there. I even have this in my .bash_profile:

export PATH="$HOME/.cargo/bin:$PATH"

I'm guessing maybe vscode runs them as a different user?

[KalitaAlexey]

@jonathandturner,
It depends on how you start vscode.
Could you try to start it from the terminal?
I couldn't make it work on my Ubuntu when I start it from the Launchpad.

[sophiajt]

@KalitaAlexey - I'm not sure if there should be a requirement for how vscode is started for the functionality to work. Sounds like one that should work regardless of how you start vscode.

[KalitaAlexey]

@jonathandturner,
It may be VSCode problem.
However, it sounds correct that an application started not from the terminal does not get environment variables set in the specific terminal files.
What do you think?

[KalitaAlexey]

I'm closing the issue since there is no issue at all.
Feel free to open it again.

[sophiajt]

I don't understand. Your plugin was having issues detecting if rustup was installed. Are you saying you can't repro this issue?

You listed a workaround which I pointed out would not work for the general use case.

[KalitaAlexey]

@jonathandturner,Checkout #231.
It's not a problem of the extension or VSCode.
If you have some environment variables in your terminal and start some command within the terminal, the command will have access to your environment variables.
If you start some command from other place (Launchpad, Dash), the command will not have access to your environment variables declared for terminal.
It's that simple.

[fragrans]

I had a similar issue. I think it's because I'm using zsh so my path is set in zshrc instead of .bash_profile or whatever, I'm fairly new to vscode so I'm not sure how it grabs things. I solved it by including the path to the executable.

    "rust.rls": {
            "executable": "~/.cargo/bin/rustup",
            "args": ["run", "nightly", "rls"],
    },

"rust-client.rustupPath": "~/.cargo/bin/rustup"