beginners 2024-04-30 | Slack Archive

Ruben Sevaldson10:04:51

Is it expected behavior that exceptions in threads are not logged anywhere? When I evaluate this in the REPL, there is no indication that an exception happened

(async/thread (throw (ex-info "hello" {})))

While this prints the exception with stack trace to the REPL

(async/go (throw (ex-info "hello" {})))

Ed10:04:57

Yes, this is the behaviour of JVM threads. You can add an exception handler for uncaught exceptions. See https://stuartsierra.com/2015/05/27/clojure-uncaught-exceptions

Ruben Sevaldson10:04:11

Nice, thanks 👍

👍 1

m3tti15:04:14

Is there anything like a blog entry that describes how the js runtime of clojure does the reload of function or how figwheel works.

john15:04:26

Fogus had a bunch of good articles on it. Here's one: https://blog.fogus.me/2012/04/25/the-clojurescript-compilation-pipeline/

john15:04:43

Search around for his others though

john15:04:11

It's not figwheel specific, but mostly the same principles

m3tti15:04:33