Skip to content
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.

Network failure can cause "impossible" unavailable components #122

Open
brson opened this issue Sep 2, 2016 · 1 comment
Open

Network failure can cause "impossible" unavailable components #122

brson opened this issue Sep 2, 2016 · 1 comment

Comments

@brson
Copy link
Contributor

brson commented Sep 2, 2016

See rust-lang/rustup#708 where cargo didn't exist.

The most likely reason for this to happen is that the network request in live_package_url failed. It should probably have a retry loop and not be allowed to fail for any package in the host_list.

@brson
Copy link
Contributor Author

brson commented Sep 2, 2016

Actually, the exact criteria for not being allowed to fail is probably complex. Tier 1 targets can't fail. Other targets can fail, but then every single package for that target also needs to fail. It's not valid for required components to be listed as unavailable if the package they belong to is available.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant