findFailure result is used exclusively, ignoring new traceback

[Peaker]

findFailure finds the old failure that was raised. Then, if a failure is found, it uses it as the failure, and dumps any new traceback information.

It might make more sense to chain the failures so that both tracebacks exist.

In older Twisted, inlineCallbacks used to give only the traceback within the generator and the code that errback'd its deferred (without the traceback of the failure that is being errback'd). In newer Twisted, inlineCallbacks now gives only the traceback within the failure that was errback'd.

It could be nicer to have both tracebacks via Failure chaining.

[radix]

Hi Peaker. Do you think you could provide a self-contained example or even a unit test showing the problem?

[Peaker]

Sorry, I am not going to be involved with Twisted for the next while...