This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-30
Channels
- # adventofcode (4)
- # aleph (1)
- # announcements (6)
- # babashka (11)
- # beginners (63)
- # calva (73)
- # clj-kondo (9)
- # clj-on-windows (20)
- # cljdoc (8)
- # cljsrn (4)
- # clojure (48)
- # clojure-europe (20)
- # clojure-italy (1)
- # clojure-nl (11)
- # clojure-spec (11)
- # clojure-uk (3)
- # clojurescript (32)
- # cloverage (1)
- # conjure (1)
- # cryogen (5)
- # datomic (83)
- # fulcro (28)
- # graphql (23)
- # gratitude (4)
- # helix (15)
- # honeysql (4)
- # improve-getting-started (14)
- # introduce-yourself (3)
- # jackdaw (5)
- # kaocha (11)
- # leiningen (1)
- # malli (1)
- # meander (5)
- # off-topic (18)
- # pathom (17)
- # pedestal (6)
- # polylith (15)
- # practicalli (1)
- # quil (2)
- # reitit (4)
- # releases (6)
- # shadow-cljs (38)
- # sql (20)
- # testing (6)
- # timbre (5)
- # tools-deps (11)
- # vim (2)
Hi everyone; is this channel active? Anyway - I was surprised to find that the logs produced from the JVM's uncaught exception handler thread does not honor the timbre configuration configured in the main thread and honorod by all the other threads. IE - I install a json appender which works on most threads, but the log statement in the uncaught exception handler uses the default timbre config. Is this something that I must fix? How can I apply the config in all threads?
@pieterbreed I haven't had that problem. Are you doing something like this?
(timbre/merge-config! ...) ; set timbre config
(Thread/setDefaultUncaughtExceptionHandler
(reify Thread$UncaughtExceptionHandler
(uncaughtException [_ thread ex]
(timbre/error ex "Uncaught exception on thread" (.getName thread)))))
that's the essence of what I do yes.
I just reduced the code I run to the essence and it seems to work correctly. Like always it seems that my code is broken. Thanks for the prompt, if something interesting comes up, I'll report it here.