This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-03
Channels
- # boot-dev (1)
- # cider (27)
- # cljsjs (6)
- # cljsrn (11)
- # clojure (249)
- # clojure-dusseldorf (1)
- # clojure-finland (1)
- # clojure-greece (1)
- # clojure-italy (28)
- # clojure-nl (12)
- # clojure-russia (2)
- # clojure-spec (5)
- # clojure-uk (27)
- # clojurescript (24)
- # clojutre (2)
- # component (8)
- # cryogen (1)
- # cursive (7)
- # datomic (61)
- # editors (18)
- # emacs (1)
- # events (1)
- # figwheel (4)
- # fulcro (35)
- # graphql (4)
- # jobs (3)
- # jobs-rus (1)
- # keechma (1)
- # leiningen (1)
- # london-clojurians (1)
- # luminus (62)
- # off-topic (154)
- # onyx (23)
- # pedestal (43)
- # portkey (66)
- # re-frame (49)
- # reagent (23)
- # shadow-cljs (92)
- # tools-deps (113)
- # uncomplicate (2)
does anybody else consistently see nil
causes on exceptions thrown during startup?
i.e., I see component's wrapped exception but can't find the underlying so I don't know what actually went wrong
based on this code that seems impossible, but I see this basically all the time https://github.com/stuartsierra/component/blob/component-0.3.1/src/com/stuartsierra/component.cljc#L116
but no, I don't think I've seen that, I might also look at however the exception is being reported (logging, some exception pretty printer) some of those do terrible things
It's not missing just a stacktrace but the whole throwable. I can get the ex-info thrown by component and call getCause and it's nil
I guess I'll try debugging it next time since apparently I'm the crazy one