-
Notifications
You must be signed in to change notification settings - Fork 4
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
Can get non-json and puke non-informatively #192
Comments
@yarikoptic Depending on what information you want to see (presumably the non-JSON response body?), we could just call For the record, the fact that the error states |
ah, cool... let's see if we ever run into such a case again first which would indeed require
not necessarily I think:
|
from cron email
am I right that it is happening at requests level and thus we likely can't do anything to make crash more informative?
The text was updated successfully, but these errors were encountered: