Found 15 possible answers.
|User||Answered At||Possible Answer|
- no i mean, how are you getting that exception?
- assuming you knew that the ret value was the form of an exception, then if you get one of those, it failed and maybe it is needed and we’ll find that and it will change I’m not trying to be a pain about this, really just trying to push against adding more stuff if it’s not actually needed maybe relevant to have a predicate to ask: does this map represent an exception? in all of these cases (exception during read, exception during eval, return value is an exception), a repl does the same thing: it prints the exception I’m not sure that it’s relevant whether it failed during read or evaluation
- Hmmm, why is there no differentiation between a thrown exception value and a returned exception value? in prepl
- What was the exception attached to the stack?
- the first thing I’d have a look at is the memory tab / under GC times Any idea what the exception was in this case? I didn’t realise that your job is actually being killed. That suggests you might need a handle-exception lifecycle to stop it from being killed when it throws an exception (depending on the exception)
- Is it considered good practice to catch an exception in a low-level namespace (e.g. Catch unique constraint exception in db namespace) and rethrow it as another custom domain exception (e.g. username-already-taken) that your route handlers can understand and present to the user?
- Can't you set the default exception handler for that?
- well if Clojure is slow than Clojure in Clojure (pods) what is it?
- Which line or object is throwing the exception?
- ```Caused by: java.lang.NoClassDefFoundError: clojure/java/api/Clojure ```@zilti is that the exception you’re seeing as well?