This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-05
Channels
- # bangalore-clj (2)
- # beginners (132)
- # boot (311)
- # cider (5)
- # cljs-dev (27)
- # cljsjs (2)
- # cljsrn (16)
- # clojure (76)
- # clojure-art (1)
- # clojure-france (8)
- # clojure-russia (35)
- # clojure-spain (3)
- # clojure-spec (2)
- # clojure-uk (11)
- # clojureindia (1)
- # clojurescript (98)
- # core-async (3)
- # css (9)
- # cursive (9)
- # datascript (7)
- # datomic (7)
- # emacs (30)
- # jobs (1)
- # lein-figwheel (7)
- # london-clojurians (1)
- # lumo (14)
- # off-topic (6)
- # om (1)
- # planck (3)
- # protorepl (1)
- # re-frame (27)
- # reagent (17)
- # spacemacs (10)
- # untangled (1)
- # yada (16)
@ska Could it be that anything in state/prq-unqueued
or process-the-thing
threw a java.lang.Error
or any other class that isn't in the inheritance chain of java.lang.Exception
? That would also explain the observed behavior.
@dergutemoritz Good idea. I am actually catching Exception
and not Throwable
. But I also install a Thread$UncaughtExceptionHandler
that would log. My understanding is, that there should be no way of falling through this, but of course I may be wrong.
@ska Indeed, you should get a log that way AFAICT