Fork me on GitHub
#cider
<
2023-02-05
>
mkvlr17:02:53

When augmenting an existing exception my cider doesn’t show me the new ex-message but only the original one. This makes it often hard to see what’s going on. Do other folks have the same behaviour? Is this intentional?

mkvlr17:02:25

I can tap to a much nicer display, any way to make that the default?

mkvlr18:02:02

if I rethrow without ex-cause I do see the more specific ex-message but I’d prefer to not lose the ex-cause

dpsutton19:02:47

Have to check how the source works. Probably comes from the underlying clojure tooling which behaves this way to show you the actual error and not the wrappers around it

mkvlr20:02:40

shouldn’t it be the other way around? Augmenting and rethrowing should typically add information and improve the message?

dpsutton20:02:41

Maybe. If a tls connection throws so your connection throws so your query throws so your endpoint throws, you ideally want the tls connection issue. The others lack any context

👍 2