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

provider/aws: Fix all pointer RetryError returns #5538

Merged
merged 1 commit into from
Mar 9, 2016

Conversation

phinze
Copy link
Contributor

@phinze phinze commented Mar 9, 2016

All of these RetryErrors were meant to fail right away, but instead
caused retry looping because the typecheck in the implementation of
resource.Retry() only catches the value type, and not the pointer
type.

Refs #5537

@jen20
Copy link
Contributor

jen20 commented Mar 9, 2016

Also refs #5537.

All of these RetryErrors were meant to fail right away, but instead
caused retry looping because the typecheck in the implementation of
`resource.Retry()` only catches the value type, and not the pointer
type.

Refs #5537
@phinze phinze force-pushed the phinze/retryerror-pointers-are-evil branch from e637848 to de65694 Compare March 9, 2016 21:00
phinze added a commit that referenced this pull request Mar 9, 2016
…e-evil

provider/aws: Fix all pointer RetryError returns
@phinze phinze merged commit ffa5db4 into master Mar 9, 2016
@phinze phinze deleted the phinze/retryerror-pointers-are-evil branch March 9, 2016 22:53
@ghost
Copy link

ghost commented Apr 27, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants