Currently IndexBounds::isValidFor runs 4 different validations when evaluating bounds validity for a given field. When validation fails, a tripwire assertion is triggered. This seldom occurs but when it does, such as in BF-38867, it is very hard to reproduce and we have no information about which of the 4 validations did indeed fail. Adding logging when the validation is about to fail would be very beneficial next time this issue happens.
Increase logging when index bounds are deemed invalid
ExportXML Word Printable JSON
- Assignee:
-
Carlos Alonso Pérez
- Reporter:
-
Carlos Alonso Pérez
- Votes:
-
0 Vote for this issue - Watchers:
-
5 Start watching this issue
- Created:
- Updated:
- Resolved: