Opened 7 years ago

Last modified 5 years ago

#2853 defect new

findFailure result is used exclusively, ignoring new traceback

Reported by: Peaker Owned by:
Priority: normal Milestone:
Component: core Keywords:
Cc: Branch:
Author: Launchpad Bug:

Description

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.

Change History (3)

comment:1 Changed 6 years ago by radix

  • Owner changed from glyph to Peaker

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

comment:2 Changed 5 years ago by Peaker

  • Owner changed from Peaker to radix

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

comment:3 Changed 4 years ago by <automation>

  • Owner radix deleted
Note: See TracTickets for help on using tickets.