It seems that changes made in #115 don't handle exceptions well when it's an exception outside of the clj-http exceptional status codes, e.g. when it's a pure Java exceptions like UnknownHostException or something related to connection timeouts. Such exceptions get caught, but the verbosity output messes up with getting exception info, so that the output may look like:
It seems that changes made in #115 don't handle exceptions well when it's an exception outside of the clj-http exceptional status codes, e.g. when it's a pure Java exceptions like
UnknownHostExceptionor something related to connection timeouts. Such exceptions get caught, but the verbosity output messes up with getting exception info, so that the output may look like: