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.

Sign up for GitHub

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

Jump to bottom

Library crashes on Too Many Requests response #20

Open
m-aciek opened this issue Sep 19, 2019 · 0 comments · May be fixed by #21
Open

Library crashes on Too Many Requests response #20

m-aciek opened this issue Sep 19, 2019 · 0 comments · May be fixed by #21

Comments

@m-aciek
Copy link

m-aciek commented Sep 19, 2019

getUser throws hyperwallet.exceptions.HyperwalletAPIException: Invalid Content-Type specified in Response Header when Hyperwallet server internally returns Too Many Requests.

It could raise some catchable exception instead.

application_1       | Traceback (most recent call last):
application_1       |   File "/usr/local/lib/python3.7/site-packages/hyperwallet/api.py", line 117, in getUser
application_1       |     os.path.join('users', userToken)
application_1       |   File "/usr/local/lib/python3.7/site-packages/hyperwallet/utils/apiclient.py", line 156, in doGet
application_1       |     params=params
application_1       |   File "/usr/local/lib/python3.7/site-packages/hyperwallet/utils/apiclient.py", line 116, in _makeRequest
application_1       |     self.__checkResponseHeaderContentType(response)
application_1       |   File "/usr/local/lib/python3.7/site-packages/hyperwallet/utils/apiclient.py", line 208, in __checkResponseHeaderContentType
application_1       |     raise HyperwalletAPIException('Invalid Content-Type specified in Response Header')
application_1       | hyperwallet.exceptions.HyperwalletAPIException: Invalid Content-Type specified in Response Header
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Handle 429 status code in response gracefully. m-aciek/python-sdk
1 participant
@m-aciek