epriestley 56bcb33a18 Improve exception reporting behavior for core exceptions ... Summary: See <https://github.com/facebook/phabricator/issues/487>. If an exception is thrown too high in the stack for the main exception handling to deal with it, we currently never report a stack trace. Instead: - Always report a stack trace to the error log. - With developer mode, also report a stack trace to the screen. Test Plan: Added a high-level `throw` and hit both cases. Got traces in the log and traces-under-developer-mode on screen. Reviewers: btrahan Reviewed By: btrahan CC: aran Differential Revision: https://secure.phabricator.com/D8022		2014-01-21 14:03:09 -08:00
..
aphlict	Remove spurious "+x" from files that shouldn't have it	2013-10-05 05:18:17 -07:00
bin	Ignore and README for support/bin	2013-04-03 12:58:39 -07:00
empty	Specify HOME when invoking Git commands	2013-05-21 14:14:31 -07:00
jshint	Use JsShrink if jsxmin is not available	2013-05-18 17:04:22 -07:00
phame	Delete license headers from files	2012-11-05 11:16:51 -08:00
PhabricatorStartup.php	Improve exception reporting behavior for core exceptions	2014-01-21 14:03:09 -08:00