A new error ResultFailedError is introduced. It will be raised when using a Result object after the result or another result in the same transaction has failed.
User code would only ever run into this situation when catch exceptions and deciding to ignore them. Now, an error will be raised instead of undefined behavior. The undefined behavior before this fix could be (among other things) protocol violations, incomplete summary data, and hard to interpret errors.
A new error
ResultFailedErroris introduced. It will be raised when using aResultobject after the result or another result in the same transaction has failed.User code would only ever run into this situation when catch exceptions and deciding to ignore them. Now, an error will be raised instead of undefined behavior. The undefined behavior before this fix could be (among other things) protocol violations, incomplete summary data, and hard to interpret errors.
Depends on: