rami3l

@rustbot claim

I've been using the `Captures` hack (https://github.com/rust-lang/rust/issues/66551#issuecomment-629815002) since a long time ago, but since `use` has been a part of the language now, I guess the original problem has been...

I guess running `rustup set auto-self-update disable` first might mitigate this issue, as per the [user guide](https://rust-lang.github.io/rustup/basics.html?highlight=auto-self-update#keeping-rustup-up-to-date).

Looks like this probably has something to do with #2441?

The error messages comes from: https://github.com/rust-lang/rustup/blob/3f572994fc42e23760e40fd3baadfd935a5585ef/src/cli/self_update.rs#L806-L822 I have a feeling that this has something to do with how GitHub prepares its Windows images. For example, it might be tricking Rustup...

As a mitigation has been implemented in https://github.com/rust-lang/rustup/pull/3907, starting from v1.28 this error will no longer happen (although updating from v1.27 to v1.28 doesn't count, since the business logic in...

> @rami3l so probably okay to close this issue, then? @djc Makes sense. Closing in favor of #988.

@Patitotective I'm just coming by to say that the latest luautf8 might have some compatibility issues with this plugin, however here is a quick approach to install a pinned version...

> Components aren't installed into isolated directories - they all exist under the toolchain root. > > If you want the path to a binary, `rustup which rustc` already exists....

@sohang3112 May I ask what you are using these paths for? > TIL about `rustup doc --path` - is this mentioned in the documentation? Not yet, but there probably should...