mschurr / spark-whoops Goto Github PK

For exceptions that were caused by another (Exception::getCause does not return null), we should also render those in the error report.

By default, select the stack to display that is closest to the top and has code to display as this will in most cases be the most relevant frame for the user to see.

Can catch Errors this way as well.

@perwendel @tipsy: Can you enable issue tracking on the fork @ https://github.com/perwendel/spark-debug-tools? (Click Settings, check Enable Issues)

Also (as for the issue to report): can you make sure that the debug screen sets the response status to HTTP 500 Internal Server Error? This should ensure that AJAX handlers/REST clients will properly detect the failure when the debug screen is displayed.

We've forked the project now, and we're aiming to release it together with 2.4. Thank you very much for your work on this @mschurr.

Currently, we are only looking within $cwd/src/main/java

I just cloned the repo and tried to run the example:

All the HTML/CSS/JS stuff seems to be missing.