-
Notifications
You must be signed in to change notification settings - Fork 36
fix: requests error handling #82
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
Conversation
c16f660 to
bb91457
Compare
bb91457 to
83a68bf
Compare
a4590a8 to
8bda0c4
Compare
8bda0c4 to
25ed107
Compare
4a5c80b to
2ecdcbe
Compare
858bc3e to
ab1df06
Compare
ab1df06 to
37d45dd
Compare
37d45dd to
bf9bf5c
Compare
| else: | ||
| reason = response.reason | ||
|
|
||
| if 200 < status_code <= 399: |
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.
So only 200 would be expected code?
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.
yes, as successful, in this specific request.
stsantilena
left a comment
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.
Just another small clarification. Other than that LGTM.
LOG-11814