Closed Globegitter closed 8 years ago
We are using a Future that is not neither a ConcurrentFuture or an AsyncIOFuture, but a GRPC future (https://github.com/grpc/grpc/blob/d0fbba52d6e379b76a69016bc264b96a2318315f/src/python/grpcio/grpc/framework/foundation/future.py#L63). This allows for any Future that implements add_done_callback to be used and resolves our issue.
ConcurrentFuture
AsyncIOFuture
add_done_callback
Coverage increased (+0.6%) to 94.805% when pulling 04690be86b353700bbe9687de25cfa611b2c476b on Globegitter:patch-1 into 127a202f553f073e5c891231c8227c6800d4c210 on syrusakbary:master.
We are using a Future that is not neither a
ConcurrentFuture
or anAsyncIOFuture
, but a GRPC future (https://github.com/grpc/grpc/blob/d0fbba52d6e379b76a69016bc264b96a2318315f/src/python/grpcio/grpc/framework/foundation/future.py#L63). This allows for any Future that implementsadd_done_callback
to be used and resolves our issue.