rami3l

@zanieb As a part of Rustup's plan for the v1.28.0 release cycle, I've migrated Rustup to `aws-lc-rs` in https://github.com/rust-lang/rustup/pull/3898 for the very same reason (https://github.com/rust-lang/rustup/issues/3820), and I've been contacting `aws-lc`'s...

I believe all work required in this repo has concluded in #3920. As such, I'm closing this issue as completed now. For further work, please refer to https://github.com/rust-lang/rust/pull/126856.

Windows Terminal 1.18 is available today. Do you think the issue can be safely closed now, @konnorandrews? cc @ryanavella

As there are currently no further actions that can be taken from our side with respect to this issue, I'm closing it now as stale. Please feel free to reopen...

FYI, now it's easier to parse `rustup`'s output if you want to script the behavior: - https://github.com/rust-lang/rustup/issues/3519 - https://github.com/rust-lang/rustup/pull/3862

> It is a bit of a strange error. Experimenting: > > ``` > djc-2021 ~ $ rustup add -h > error: invalid value 'add' for '[+toolchain]': error: "add" is...

AFAIK `tcsh` isn't even POSIX, so supporting that falls into the same category as supporting `fish`, meaning that: - The `source` suggestion is incorrect anyway (even worse than #3415) because...

@Modicrumb Thanks for your investigation! Probably a duplicate of https://github.com/rust-lang/rustup/issues/3125 then.

> RUSTUP_USE_RUSTLS=1 seems to be another workaround with last rustup version. Without any envvars setted problems still persist @llde That kinda makes sense since the current default is to use...

@djc @ChrisDenton I'm not quite sure what happened here, but could this be related to https://github.com/rust-lang/rustup/pull/4023 (since a fresh reinstallation works alright but not an upgrade)?