Vernon Lyon

> If I'm not mistaken this is basically the discussion held in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697871, or am I wrong ? Actually this is discussed here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830518, but is related to the one...

See related issue #21

I have found a workaround for this issue, and have been using it for some time now on Debian. I use a simple perl script that I've written, to send...

Please note, there is one thing this PR doesn't address: Changes to the css in `share/skel/public/css/error.css` won't get picked up by apps that have already been created. This is not...

@xsawyerx Most of the code has been "borrowed" from Miyagawa's [Plack::Middleware::StackTrace](https://metacpan.org/pod/Plack::Middleware::StackTrace) The `SIG` handler is the only dependable way that I know to generate a stack-trace at the point of...

@xsawyerx Regarding `error.css`: > Maybe we can introduce a way in `dancer2` to update your static files if they're a known older version? We don't want to have to create...

Hi @xsawyerx, I'm glad you don't want to give up on it. I'm also willing to split it into 2 smaller PRs. 1. Delete `error.css` and move all the style...

Ok, well that brings us back to using the patch as it is. Can we at least use the first commit 0e0570876e0cc48c447e39d18d17da44f91b7c68 in this PR? It doesn't really _need_ the...

Actually lets break this into 2 PRs. 1. Error formatting #1146 2. Coming soon ...

True, this change does nothing for logging, and yes, it makes no changes to exception handling. What it _does_ do is change the displayed stack-trace, which is currently incorrect. This...