fix: set skew offset in catch block upon failure

[kgoedecke]

Issue

#2208

Description

The time skew wasn't correct since the await block got rejected upon a request that has a skewed time. Hence we need to correct the time inside a catch block for it to succeed on the next try.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (main@af23369). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2664   +/-   ##
=======================================
  Coverage        ?   60.60%           
=======================================
  Files           ?      516           
  Lines           ?    27780           
  Branches        ?     6826           
=======================================
  Hits            ?    16836           
  Misses          ?    10944           
  Partials        ?        0           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af23369...c175b63. Read the comment docs.

[AllanZhengYP]

@kgoedecke Looks like the existing unit tests for clock skew is failing. Can you take a look at them?

[aws-sdk-js-automation]

AWS CodeBuild CI Report

• CodeBuild project: sdk-staging-test
• Commit ID: c175b63
• Result: FAILED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[trivikr]

Thank you @kgoedecke for posting this PR.

Your commit was cherry-picked in subsequent PRs as explained in #2208 (comment)

This PR will be closed when the fix is posted upstream.

[trivikr]

Superceded by #2686

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.