Closed jasononeil closed 10 years ago
The above code kind of works if you use -D PromhxExposeErrors
(though is stil a fairly ugly solution... a way of passing the stack trace to the reporter would be better).
I've been trying to catch async exceptions using promhx, but I cannot figure it out exactly, especially when it's thrown on another thread as in Neko... maybe we can enlist the help of @jdonaldson?
This and #10 is fixed now in version 0.9.0, but for synchronous exceptions only. I left a note in the FAQ explaining why.
Great, thank you!
When dealing with exceptions in async code I find it easier to use Promise<Outcome<SuccessType,ErrorType>>
or similar anyway - exceptions in async code are always going to be a bit ugly.
I tried to do this:
But the async code swallows up the exception stack and I'm not familiar enough with promhx to know where to look next :)