use Debug impl for generic Reqwest errors to provide more info

see https://github.com/apache/arrow-rs/issues/6377

This should help in the interim to identify specific causes of, sometimes confusing, network
related errors. I think this change should be temporary until we can find a better way to
improve error messages.

Author: erratic-pattern

object_store/src/client/retry.rs

@@ -39,7 +39,7 @@ pub enum Error {
         body: Option<String>,
     },
 
-    #[snafu(display("Error after {retries} retries in {elapsed:?}, max_retries:{max_retries}, retry_timeout:{retry_timeout:?}, source:{source}"))]
+    #[snafu(display("Error after {retries} retries in {elapsed:?}, max_retries:{max_retries}, retry_timeout:{retry_timeout:?}, source:{source:?}"))]
     Reqwest {
         retries: usize,
         max_retries: usize,
@@ -174,7 +174,6 @@ impl Default for RetryConfig {
             backoff: Default::default(),
             max_retries: 10,
             retry_timeout: Duration::from_secs(3 * 60),
-        }
     }
 }
 

object_store/src/http/client.rs

@@ -40,7 +40,7 @@ enum Error {
     #[snafu(display("Request error: {}", source))]
     Request { source: retry::Error },
 
-    #[snafu(display("Request error: {}", source))]
+    #[snafu(display("Request error: {:?}", source))]
     Reqwest { source: reqwest::Error },
 
     #[snafu(display("Range request not supported by {}", href))]