component 2018-05-03

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

do you have that jvm option turned off where it sometimes omits stracktraces?

-XX:-OmitStackTraceInFastThrow

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