rami3l

Unfortunately, @fbrv just DM'd me and expressed their wish of backing out due to a personal incident. Thanks anyway for having offered to help!

> Could I try this? @Xerxes-2 Yes, please!

> I think a good approach here would be to add an integration test that can download a recent manifest, parse it, and regenerate a source file that contains current...

@djc After some investigation I think https://docs.rs/platforms could potentially be a better alternative, also I like its glob patterns which might greatly simplify our Implementation. I'm not sure how this...

So here's my plan for the experiment: I'll try to generate a source file by CS 101-level string templating according to the rules in https://github.com/rust-lang/rustup/issues/3783#issuecomment-2084304503, and `include!()` it in `src/dist/triple.rs`....

> Instead of using `include!()` or a procedural macro, IMO it would be better to have an integration test that writes into a source file inside `src` and can be...

@fh-igd-mueller-roemer Thanks for the report anyway! Looks like a @rust-lang/infra problem though...

@jdno `curl -4` can solve the sh.rustup.rs issue, but for this situation regarding static.rust-lang.org in particular, is there a reasonable workaround? (For example, is setting the environment variable `RUSTUP_UPDATE_ROOT=https://fastly-static.rust-lang.org/rustup` a...

@kLiHz Thanks for your interest! However, as I mentioned above, the website and its deployment is out of the Rustup Project's control. Maybe the `t-infra` channel on the official Zulip...

I think the artifact size changes are acceptable even if we keep `opentelemetry`: ### BEFORE ### AFTER