Be able to retry on errors other than Auth0::RateLimitEncountered?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ruby
- Domain
- api, authentication
Research direction
Start by locating the Ruby Auth0 retry handling that currently uses Auth0::RateLimitEncountered and review how RestClient::RequestTimeout is surfaced. Confirm the desired optional error-class condition and verify the behavior with the existing test suite; done means retries can be configured for the requested error without changing the current default.
Written by the indexing model from the issue text.
Description
Checklist
- I have looked into the Readme and Examples, and have not found a suitable solution or answer.
- I have looked into the API documentation and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
Describe the problem you'd like to have solved
I want to optionally control whether or not retries are performed when RestClient::RequestTimeout occurs instead of Auth0::RateLimitEncountered.
Describe the ideal solution
As a condition of retry, option to be executed in another error class.
Alternatives and current workarounds
No response
Additional context
No response
- Dominant language
- Ruby
- Stars
- 205
- Forks
- 148
- Avg merge
- 13h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from auth0/ruby-auth0
-
Model#initialize drops every `false` value — booleans are silently lost on requests and responsesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
auth0/ruby-auth0#800 · 1 comment ·
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 45/100
auth0/ruby-auth0#709 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 50/100
auth0/ruby-auth0#610 · 1 comment ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 32/100
auth0/ruby-auth0#606 · 2 comments · 1 reaction ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
auth0/ruby-auth0#556 · 2 comments ·
All issues in auth0/ruby-auth0
Similar issues
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
OSCON 2016Opencontent
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
rubyevents/rubyevents#2148 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
we-promise/sure#3838 · 2 comments ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ManageIQ/manageiq-ui-classic#10341 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
rubocop/ruby-style-guide#984 ·