Skip to content

fix(gc): retry aws serialization error if wrapped as aws request failure

Suleimi Ahmed requested to merge 753-retry-wrapped-serialization-error into master

Related to #753 (closed)

This MR builds on the work of #753 (closed) by addressing some of the newer requirements mentioned here.

Context

The AWS-SDK is sending an error of type awserr.RequestFailure that wraps an errCodSerializationError when we are expecting an explicit errCodSerializationError. We would like to retry awserr.RequestFailure that are intrinsically errCodSerializationError following the conversation here. This should increase the chances of completing offline gc runs for customers that are experiencing a connection reset by peer from S3 of the nature:

 SerializationError: failed to decode REST XML response │     status code: 200, request id: XXXXXXXXXXXX

Merge request reports