We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If there is an exception that is thrown inside of a http-kit response callback, nothing is ever logged anywhere (unless it is derefed).
(deftest exception-handling (testing "Inside fake-http" (fake-http/with-fake-http ["https://google.com" 200] (http/get "https://google.com" (fn [resp] (throw (Exception. "Inside logged?")))))) (testing "outside fake-http" (http/get "https://google.com" (fn [resp] (throw (Exception. "Outside logged?"))))))
Ran 1 test containing 0 assertions. No failures. Wed Apr 26 16:05:48 CDT 2017 [client-worker-2] ERROR - GET https://www.google.com/'s callback java.lang.Exception: Outside logged?
Inside responder-wrapper it may just be appropriate to log similar to how http-kit does:
responder-wrapper
(try ((or callback identity) %1) (catch Throwable e ;; dump stacktrace to stderr (HttpUtils/printError (str method " " url "'s callback") e) ;; return the error {:opts opts :error e}))
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue
If there is an exception that is thrown inside of a http-kit response callback, nothing is ever logged anywhere (unless it is derefed).
Steps
Output
Possible Solution
Inside
responder-wrapper
it may just be appropriate to log similar to how http-kit does:The text was updated successfully, but these errors were encountered: