rami3l

@epage I think it's hard to explain that `+toolchain` is a rustup feature rather than a `cargo` one; I didn't know that before taking the responsibility here. The original help...

@epage So I'm trying to think from @sliedes' perspective here: * They've got the following hint; that's a good sign but they're not sure what "invoke `cargo` through `rustup`" means......

> Why couldn't we just make `rustup +nightly run cargo miri test` do the right thing? @djc I agree that a redesigned `rustup run` command shouldn't take the toolchain name...

@xobs I'm sorry but I haven't fully understood your request. What was the error message you were getting? Are you sure the entries that you need are really in the...

@xobs Okay I think I have the full picture now. Trying this on the bleeding release of `rustup` gives: ```console > RUSTUP_DIST_SERVER=https://xous.xobs.io/dist rustup +stable target install riscv32imac-unknown-xous-elf error: toolchain 'stable-aarch64-apple-darwin'...

@xobs Could you try to log the line where `rustup` is getting the manifest file though? The log you have shown above seems to be only related to component downloading.

@xobs We do allow mirrors or third-party release servers, for example [TUNA](https://mirrors.tuna.tsinghua.edu.cn/help/rustup/) has been using the same mechanism without problems... so your use case should be valid as well in...

@xobs Just in case you doubt the manifest reading doesn't work, see the log below: ```console > RUSTUP_LOG=rustup=debug RUSTUP_DIST_SERVER=https://xous.xobs.io/dist rustup toolchain install beta 2025-12-09T15:07:56.153260Z DEBUG rustup::config: read metadata version: 12...

> Maybe have something similar to how we do environment variables for things like `CARGO_TARGET__RUNNER` where a dist server can be different for a target triple? @xobs I'm afraid that...

> I'm not sure that works, but I'm not entirely understanding the proposal. How would that allow for installing a `+stable` toolchain for tier-3 targets? The proposal looks like a...