Ticket #6164 enhancement new
Returning an already-chained deferred breaks the callback chain
|Reported by:||radix||Owned by:|
(diff, github, buildbot, log)
If d1 has a callback that returns d1, the callback chain will halt, meaning no further callbacks on that Deferred will ever be run (as far as I can tell; I haven't figured out any other way to un-stick the Deferred).
We should warn the user in this case.
That's the easy one. You can also do an indirect Deferred chain -- d1 returning d2 from a callback which itself has a callback that returns d1. This continues to "work", but it's probably still always a bad thing to do. If we can warn the user in this case too, that'd be nice.