- 🇦🇹Austria drunken monkey Vienna, Austria
OK, I guess this does make sense. We want as little chance as possible of something just terminating the whole indexing process, and as we can’t guarantee that other code doesn’t contain fatal bugs, we should just catch everything we can.
Little problem is that we’d also need to adapt the signature of
LoggerTrait::logException()
to still be able to use it with\Error
instances as well. However, for a trait, I don’t think such a change is a BC problem at all, since overriding trait methods works differently than for classes/interfaces. However, I still created a change record → for it.Please test/review!
The last submitted patch, 6: 3252430-6--render_item_processor_catch_all_throwables.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- Status changed to Fixed
almost 2 years ago 2:49pm 19 March 2023 Automatically closed - issue fixed for 2 weeks with no activity.