Richard van der Hoff f22e7cda2c Fix a class of logcontext leaks
So, it turns out that if you have a first `Deferred` `D1`, you can add a
callback which returns another `Deferred` `D2`, and `D2` must then complete
before any further callbacks on `D1` will execute (and later callbacks on `D1`
get the *result* of `D2` rather than `D2` itself).

So, `D1` might have `called=True` (as in, it has started running its
callbacks), but any new callbacks added to `D1` won't get run until `D2`
completes - so if you `yield D1` in an `inlineCallbacks` function, your `yield`
will 'block'.

In conclusion: some of our assumptions in `logcontext` were invalid. We need to
make sure that we don't optimise out the logcontext juggling when this
situation happens. Fortunately, it is easy to detect by checking `D1.paused`.
2018-05-02 11:58:00 +01:00
..
2018-04-05 16:24:04 +01:00
2016-02-19 15:34:38 +00:00
2017-01-16 15:33:34 +00:00
2018-04-16 00:39:32 +02:00
2017-01-17 11:50:18 +00:00
2016-07-05 15:23:17 +01:00
2017-03-30 14:14:46 +01:00
2016-02-17 14:29:28 +00:00