Comments (7)
@nopeless Thanks a lot for filing this issue! It looks like a duplicate of #3791.
It would be very unreasonable to make our website IPv4-only just for your use case, but for the moment being:
You can force the protocol version with the -4 and -6 flags for curl.
cc @rust-lang/infra
from rustup.
@nopeless What's your issue exactly like?
curl
ing:
https://sh.rustup.rs
https://static.rust-lang.org/
https://cloudfront-static.rust-lang.org/
https://faslty-static.rust-lang.org/
all succeeded on my WSL 2.
WSL 2 may had broken IPv6 support, but OS and curl won't be silly enough to stick on IPv6.
And after all it's a Microsoft issue so it's not reasonable for others to clean up the mess for it.
By the way Microsoft rolled out IPv6 support in their Insider Program, try it out if you'd like.
can you curl -6?
from rustup.
I think there are probably a lot of people using rustup in WSL 2 and we haven't seen a lot of reports like yours. I don't think restricting rustup to IPv4 only based on a small minority of users (that might have other environmental issues) is the right direction. rustup is maintained by volunteers, please be constructive in your feedback.
from rustup.
Yes it could be a simple "fix". However just as there are IPv4-only situations, there could also users which only have IPv6. Should site became IPv4 only, it would be those users here to complaint. You are probably wrong here and I won't call it a fix since it breaks for others.
You could suggest adding a IPv4/IPv6 switch, or even PR one. You could also limit IP resolving on your WSL instance or elsewhere, using dnsproxy
or other kinds of proxies. Staring your own reverse proxy is also a choice, since rustup endpoints can be customised via environment variables.
And a few issue reports is not sufficient as the evidence that WSL fails on dual-stack sites. You're not providing your side of situation either. At least in another issue reporting 10054 errors on Win 11 Enterprise they tested both IPv4 and IPv6 of rust-lang.org's CDN on both faslty and AWS, and limiting the issue to IPv6 with Cloudfront.
And even it is, like I said, rustup.rs or any other sites shouldn't drop IPv6 since it would break else where and it really is a Microsoft issue.
from rustup.
@nopeless Thanks a lot for filing this issue! It looks like a duplicate of #3791.
It would be very unreasonable to make our website IPv4-only just for your use case, but for the moment being:
You can force the protocol version with the -4 and -6 flags for curl.
cc @rust-lang/infra
The installer internally uses curl as well. There is no way I can put a flag on that
from rustup.
@nopeless What's your issue exactly like? curl
ing:
https://sh.rustup.rs
https://static.rust-lang.org/
https://cloudfront-static.rust-lang.org/
https://faslty-static.rust-lang.org/
all succeeded on my WSL 2.
WSL 2 may had broken IPv6 support, but OS and curl won't be silly enough to stick on IPv6.
And after all it's a Microsoft issue so it's not reasonable for others to clean up the mess for it.
By the way Microsoft rolled out IPv6 support in their Insider Program, try it out if you'd like.
from rustup.
im ngl idk what im even doing wrong here
all i said is that wsl has these issues and its a rather simple fix from whoever manages rustup to use ipv4 only
and the response is "works on my machine" and *its a microsoft issue so we won't deal with it"
sorry
from rustup.
Related Issues (20)
- Reserve `RUSTUP_LOG` for `tracing` usages instead of `RUST_LOG` HOT 1
- Style: Decide between `foo.rs` and `foo/mod.rs` HOT 9
- Consider getting rid of `toolchain_sort()`
- Confusing error message `toolchain "stable-x86_64-unknown-linux-gnu" is not installable` HOT 9
- IBM
- Use `LevelFilter::Warn` for `stderr` if `-q` is present in `rustup-init`
- rustup segfaults when running in a linux/amd64 docker container on macOS M3 host HOT 6
- Improve handling of `clap` errors
- FreeBSD CI failure possibly caused by `rustls-platform-verifier` HOT 6
- rustup toolchain list --verbose should list why each toolchain was installed HOT 5
- Dependabot lockfile updates are gone
- Meta: Ship builds from the `master` branch as well
- Tracking: Workspace trust & safe file discovery
- Windows: "called `Option::unwrap()` on a `None` value" HOT 18
- Tracking: Ensure the integrity of toolchains, handle concurrent reads/writes HOT 2
- Proposal: `rustup toolchain verify`
- `rustc --version` should not trigger/initiate toolchain updates
- UI error - contradictory output when toolchain not found HOT 2
- Update `taplo` to v0.9
- Toolchain file not properly resolving Rust 1.79 HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rustup.