https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32777 Jonathan Druart <jonathan.druart+koha@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@ptfs-europe | |.com Status|NEW |In Discussion --- Comment #2 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- Do we need that in production as well? Do we actually have stack traces in production for other 500? If not, why? How do people debug crashes if they are not displayed? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32777 --- Comment #3 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- I am all for those stack traces. Note that the stack trace in plack-error.log often contains only a few useful lines. All the internal Plack stuff is just waste of space.. Devel::Stacktrace allows you to filter? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32777 --- Comment #5 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- (In reply to Marcel de Rooy from comment #4)

Can we proceed here?

Not sure how. We are going to display a stack trace in production, and I think we don't for other exceptions (whereas we should IMO). So maybe we should add a 'if $dev_install' condition to display the stack trace? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.