Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix shouldRetry behavior for nested errors #3017

Merged
merged 4 commits into from
Dec 18, 2019
Merged

Conversation

swami-m
Copy link
Contributor

@swami-m swami-m commented Dec 12, 2019

shouldRetryError should be using the var shouldRetry defined in outer scope and not declare another.

@skmcgrail skmcgrail self-requested a review December 17, 2019 18:22
@skmcgrail skmcgrail added the needs-review This issue or pull request needs review from a core team member. label Dec 17, 2019
swami-m and others added 3 commits December 17, 2019 10:28
`shouldRetryError` should be using the `var shouldRetry` defined in outer scope and not declare another.
@skmcgrail skmcgrail merged commit 80cb57d into aws:master Dec 18, 2019
@skmcgrail skmcgrail removed the needs-review This issue or pull request needs review from a core team member. label Dec 18, 2019
aws-sdk-go-automation pushed a commit that referenced this pull request Dec 18, 2019
===

### Service Client Updates
* `service/cloudfront`: Updates service documentation
  * Documentation updates for CloudFront
* `service/ec2`: Updates service API and documentation
  * This release introduces the ability to tag Elastic Graphics accelerators. You can use tags to organize and identify your accelerators for cost allocation.
* `service/opsworkscm`: Updates service API and documentation
  * AWS OpsWorks CM now supports tagging, and tag-based access control, of servers and backups.
* `service/resourcegroupstaggingapi`: Updates service documentation
  * Documentation updates for resourcegroupstaggingapi
* `service/s3`: Updates service documentation
  * Updates Amazon S3 endpoints allowing you to configure your client to opt-in to using S3 with the us-east-1 regional endpoint, instead of global.

### SDK Bugs
* `aws/request`: Fix shouldRetry behavior for nested errors ([#3017](#3017))
aws-sdk-go-automation added a commit that referenced this pull request Dec 18, 2019
Release v1.26.5 (2019-12-18)
===

### Service Client Updates
* `service/cloudfront`: Updates service documentation
  * Documentation updates for CloudFront
* `service/ec2`: Updates service API and documentation
  * This release introduces the ability to tag Elastic Graphics accelerators. You can use tags to organize and identify your accelerators for cost allocation.
* `service/opsworkscm`: Updates service API and documentation
  * AWS OpsWorks CM now supports tagging, and tag-based access control, of servers and backups.
* `service/resourcegroupstaggingapi`: Updates service documentation
  * Documentation updates for resourcegroupstaggingapi
* `service/s3`: Updates service documentation
  * Updates Amazon S3 endpoints allowing you to configure your client to opt-in to using S3 with the us-east-1 regional endpoint, instead of global.

### SDK Bugs
* `aws/request`: Fix shouldRetry behavior for nested errors ([#3017](#3017))
@swami-m swami-m deleted the patch-1 branch December 18, 2019 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants