tamagokun/toby

Error handling issues

tamagokun opened this issue · 0 comments

Exceptions / warnings, etc need to be handled better. Currently they seem to be captured properly, though sometimes it is really hard to track down where the error actually occured.

Sometimes when there is an error, the message is truncated, and you see the message of the exception which is normally "Rackem Exception". We don't want to see that, we want to see the error!!

If there is an inner Exception that triggers another Exception, both get logged, but only the last one is presented to the user. This behavior needs to be swapped, and any logging that is the stack of the RackemException and NOT the real error shouldn't be logged.