General improvements to help track down any errors that might happen:
Allow the logging methods to print out details of a caught exception. ✓
Make sure any method which catches an exception will still return a sensible value ✓
Make sure that any "major" user action is exception-aware and able to report issues to the user
[Issue created by Pidgeot: 2016-05-23]
[Last updated on bitbucket: 2016-08-08]
[Comment created by Pidgeot: 2016-08-08]
Removing milestone: 0.11a (automated comment)
[Comment created by Pidgeot: 2016-08-08]
Scanned through all of core just now, and it looks like that side is good enough at the moment. Marking this issue as resolved.
[Comment created by Pidgeot: 2016-07-10]
When logging stack traces, prefer to log exception information if available (see #116)
General improvements to help track down any errors that might happen:
[Issue created by Pidgeot: 2016-05-23] [Last updated on bitbucket: 2016-08-08]
[Comment created by Pidgeot: 2016-08-08] Removing milestone: 0.11a (automated comment)
[Comment created by Pidgeot: 2016-08-08] Scanned through all of core just now, and it looks like that side is good enough at the moment. Marking this issue as resolved.
[Comment created by Pidgeot: 2016-07-10] When logging stack traces, prefer to log exception information if available (see #116)
→ <<cset 3a2b7645083b>>