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

Change noRetryError for temporary errors #478

Closed
wants to merge 1 commit into from

Conversation

lavoiesl
Copy link
Contributor

  • Expose an Unwrap method to leverage go's standard unwrapping
  • Let the error escape, such that hooks and end-users can access the Temporary information.
  • Do not wrap if the error already exposes Temporary, to honour it.

The main benefit is to leverage net/*'s standard errors; most of them already expose Temporary methods.

@lavoiesl lavoiesl mentioned this pull request Oct 18, 2021
@jeevatkm
Copy link
Member

@lavoiesl I like your proposal of using errors advantages introduced in go1.13. Currently, resty has minimum support as go1.11. I want to park this improvement to Resty v3 release.

@jeevatkm jeevatkm added the v3 For resty v3 label Oct 24, 2021
@jeevatkm jeevatkm added this to the v3.0.0 Milestone milestone Oct 24, 2021
- Expose an `Unwrap` method to leverage go's standard unwrapping
- Let the error escape, such that hooks and end-users can access the
  `Temporary` information.
- Do not wrap if the error already exposes `Temporary`, to honour it.
@jeevatkm jeevatkm added v3-selected and removed v3 For resty v3 labels Mar 5, 2023
@lavoiesl lavoiesl closed this Oct 18, 2024
@lavoiesl lavoiesl deleted the seb-temp-error branch October 18, 2024 18:38
@jeevatkm
Copy link
Member

@lavoiesl please do not close, I will be merging this PR for v3 tonight.

@jeevatkm
Copy link
Member

I will do resolve conflicts and merge.

@lavoiesl
Copy link
Contributor Author

lavoiesl commented Oct 18, 2024

The PR was assigned to me and it has merge conflicts.
I no longer use resty and I'm no longer setup for Go development.
Sorry, but I have to abandon this 3 y.o. PR.
Feel free to cherry-pick my changes to another branch

@jeevatkm
Copy link
Member

Thanks, I will take care of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants