Page MenuHomePhabricator

Improve exception reporting behavior for core exceptions
ClosedPublic

Authored by epriestley on Jan 21 2014, 3:53 PM.
Tags
None
Referenced Files
F14322177: D8022.diff
Wed, Dec 18, 12:33 PM
Unknown Object (File)
Thu, Dec 12, 8:13 AM
Unknown Object (File)
Oct 25 2024, 10:45 PM
Unknown Object (File)
Oct 25 2024, 10:45 PM
Unknown Object (File)
Oct 25 2024, 10:45 PM
Unknown Object (File)
Oct 24 2024, 10:23 PM
Unknown Object (File)
Oct 19 2024, 6:23 PM
Unknown Object (File)
Oct 17 2024, 7:24 AM
Subscribers
Tokens
"Mountain of Wealth" token, awarded by btrahan.

Details

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.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped