cargo fetch --retry N #1602
Comments
|
Compare with |
sbeckeriv
added a commit
to sbeckeriv/cargo
that referenced
this issue
May 12, 2016
Dearest Reviewer, This branch resolves rust-lang#1602 which relates to retrying network issues automatically. There is a new utility helper for retrying any network call. There is a new config called net.retry value in the .cargo.config file. The default value is 2. The documentation has also been updated to reflect the new value. Thanks Becker
bors
added a commit
that referenced
this issue
May 12, 2016
Network retry issue 1602 Dearest Reviewer, This branch resolves #1602 which relates to retrying network issues automatically. There is a new utility helper for retrying any network call. There is a new config called net.retry value in the .cargo.config file. The default value is 2. The documentation has also been updated to reflect the new value. Thanks Becker
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm doing large scale distributed builds of Rust projects and have to contend with unreliable networks.
cargo fetchwill allow me to consolidate all of cargo's network access into a single command, but when running thousands of builds on AWS some will fail because of the network. Instead of open-coding a retry backoff loop it would be more convenient for cargo to do it.The text was updated successfully, but these errors were encountered: