konsti
4b19319485
In #3514 and #2755, users had intermittent network errors, but it was not always clear whether we had already retried these requests or not. Building upon https://github.com/TrueLayer/reqwest-middleware/pull/159, this PR adds the number of retries to the error message, so we can see at first glance where we're missing retries and where we might need to change retry settings. Example error trace: ``` Could not connect, are you offline? Caused by: Request failed after 3 retries Caused by: error sending request for url (https://pypi.org/simple/uv/) Caused by: client error (Connect) Caused by: dns error: failed to lookup address information: Name or service not known Caused by: failed to lookup address information: Name or service not known ``` This code is ugly since i'm missing a better pattern for attaching context to reqwest middleware errors in https://github.com/TrueLayer/reqwest-middleware/pull/159.
24 lines
658 B
Rust
24 lines
658 B
Rust
pub use base_client::{BaseClient, BaseClientBuilder};
|
|
pub use cached_client::{CacheControl, CachedClient, CachedClientError, DataWithCachePolicy};
|
|
pub use error::{Error, ErrorKind, WrappedReqwestError};
|
|
pub use flat_index::{FlatIndexClient, FlatIndexEntries, FlatIndexError};
|
|
pub use linehaul::LineHaul;
|
|
pub use registry_client::{
|
|
Connectivity, RegistryClient, RegistryClientBuilder, SimpleMetadata, SimpleMetadatum,
|
|
VersionFiles,
|
|
};
|
|
pub use rkyvutil::OwnedArchive;
|
|
|
|
mod base_client;
|
|
mod cached_client;
|
|
mod error;
|
|
mod flat_index;
|
|
mod html;
|
|
mod httpcache;
|
|
mod linehaul;
|
|
mod middleware;
|
|
mod registry_client;
|
|
mod remote_metadata;
|
|
mod rkyvutil;
|
|
mod tls;
|