Issue 233 in couchdb-python: CouchDB errors are not reported cleanly (shows up as exception from simplejson)

[couchdb...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 233 by wickedg...@gmail.com: CouchDB errors are not reported
cleanly (shows up as exception from simplejson)
http://code.google.com/p/couchdb-python/issues/detail?id=233

What steps will reproduce the problem?
1. Provoke a CouchDB timeout error:
https://gist.github.com/wickedgrey/d2c87e6ee1e7c695abae (Note: I have no
idea how to do this consistently; see
https://issues.apache.org/jira/browse/COUCHDB-2218 ).
2. Try to be reading a view when provoking the error:
https://gist.github.com/geordanr/30458322a74d3c753ab9

I don't have the actual HTTP request / response data.

I would like to have the exception convey more information about what
exactly went wrong (ie. what the HTTP status code was, the raw bytes
received, etc.) rather than getting something coming from inside simplejson.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[couchdb...@googlecode.com]

Comment #1 on issue 233 by djc.ochtman: CouchDB errors are not reported

cleanly (shows up as exception from simplejson)
http://code.google.com/p/couchdb-python/issues/detail?id=233

I guess we could start by wrapping the decode in a try-catch and raising
another exception with better data (e.g. HTTP headers and the data flowing
into the decode)?

[couchdb...@googlecode.com]

Comment #2 on issue 233 by djc.ochtman: CouchDB errors are not reported

cleanly (shows up as exception from simplejson)
http://code.google.com/p/couchdb-python/issues/detail?id=233

This issue has been migrated to GitHub. Please continue discussion here:

https://github.com/djc/couchdb-python/issues/233