Page MenuHomePhabricator

Catch exception thrown when no suitable handler available for some data value type
Closed, ResolvedPublic

Description

That's to prevent breaking the whole system when there is no suitable DV-Handler.


Version: unspecified
Severity: major
Whiteboard: u=dev c=backend p=5 s=2014-05-06

Details

Reference
bz64296

Event Timeline

bzimport raised the priority of this task from to Unbreak Now!.Nov 22 2014, 3:12 AM
bzimport set Reference to bz64296.
bzimport added a subscriber: Unknown Object (MLST).

I suggest to not have a null-handler, but instead catch the exception caused by not having a handler for some data value type. The exception should be logged using wfLogWarning (which causes tests to fail and gores into the error log in production).