fix(client): update errors before checking if retries exhuasted

This fixes an issue where we failed to include the latest
error in the `errors` vec before returning from impl_inner_call
with Error::AllAttemptsErrored. This meant that if the configured
retries was set to 0, an error would be raised with an empty
errors vec.

Tested by setting Config::retry to 0, triggering a client-side
error, and observing the errors vec contained within
Error::AllAttemptsErrored.

Author: ValuedMammal

src/client.rs

@@ -55,15 +55,15 @@ macro_rules! impl_inner_call {
                 Err(e) => {
                     let failed_attempts = errors.len() + 1;
 
+                    warn!("call '{}' failed with {}, retry: {}/{}", stringify!($name), e, failed_attempts, $self.config.retry());
+
+                    errors.push(e);
+
                     if retries_exhausted(failed_attempts, $self.config.retry()) {
                         warn!("call '{}' failed after {} attempts", stringify!($name), failed_attempts);
                         return Err(Error::AllAttemptsErrored(errors));
                     }
 
-                    warn!("call '{}' failed with {}, retry: {}/{}", stringify!($name), e, failed_attempts, $self.config.retry());
-
-                    errors.push(e);
-
                     // Only one thread will try to recreate the client getting the write lock,
                     // other eventual threads will get Err and will block at the beginning of
                     // previous loop when trying to read()