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.

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

Improve errors verbosity for Java native exceptions #116

Closed
pilosus opened this issue Dec 2, 2022 · 0 comments · Fixed by #117
Closed

Improve errors verbosity for Java native exceptions #116

pilosus opened this issue Dec 2, 2022 · 0 comments · Fixed by #117

Comments

@pilosus
Copy link
Owner

pilosus commented Dec 2, 2022

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:

[GitHub] null null
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant