-
Notifications
You must be signed in to change notification settings - Fork 47
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
feat: do not retry for client exceptions #36
feat: do not retry for client exceptions #36
Conversation
7083fe6
to
55dd0b1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making this a configurable option! Some changes are needed to pass in the config setting, and then we should be good to merge.
Signed-off-by: Ruben Romero Montes <rromerom@redhat.com>
Signed-off-by: Ruben Romero Montes <rromerom@redhat.com>
Signed-off-by: Ruben Romero Montes <rromerom@redhat.com>
337fa9a
to
dfa0dd5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies for the delay and thank you for making the requested updates! Tested and LGTM.
No problem at all. Happy to collaborate 🚀 |
fix: add explicit docker format for container building
I think most client exceptions should not be retried. When a resource is not found, not authorized or bad request errors are clear examples that a retry will not change the result and only delay the response.
This change only affects the async request_with_retry as the sync version belongs to the Morpheus SDK. This change will only affect the intel retrieval.