-
Notifications
You must be signed in to change notification settings - Fork 2.9k
IPv6-Only Hosts Fail to Build #10711
Copy link
Copy link
Closed
Labels
A-networkingArea: networking issues, curl, etc.Area: networking issues, curl, etc.C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-blocked-externalStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fixStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fix
Description
Problem
IPv6-only hosts are becoming more and more common with IPv4 cost skyrocketing. In some cases (eg Vultr's IPv6-only offerings) there's not any CG-NAT either, so cargo fails to run at all because the first thing it does is try to clone from github.com.
Proposed Solution
Look at providing a CF-wrapped git-clone domain or look at alternative hosting providers like gitlab.
Notes
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-networkingArea: networking issues, curl, etc.Area: networking issues, curl, etc.C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-blocked-externalStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fixStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fix
Type
Fields
Give feedbackNo fields configured for issues without a type.