Uh oh!
There was an error while loading. Please reload this page.
Move debug statement with blocking future.result() call to add_done_callback - #4174
Conversation
| For each message, schedule a callback with the executor. | ||
| """ | ||
| def callback_completed(future): | ||
| logger.debug('Result: %s' % future.result()) |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
lukesneeringer
commented
Oct 13, 2017
Thanks @jeffkpayne! |
jeffkpayne
commented
Oct 13, 2017
@lukesneeringer NP! Funny, though, I was just working on a unit test to test that the calls actually happen asynchronously... Should I continue with that and open a new PR? |
jeffkpayne
commented
Oct 13, 2017
It would be along the lines of: |
I would accept that as a system test (but not a unit test). :-) And yes, additional PR is of course welcome. |
lukesneeringer
commented
Oct 13, 2017
P. S. pubsub 0.28.4 is going through CI to release now. (This was a serious enough bug that I wanted it out immediately.) |
dhermes
commented
Oct 13, 2017
@lukesneeringer The Pub / Sub unit tests seem to be broken (or heisen-broken) on Python 2.7: |
…allbacks to complete. Guessing this test was succeeding before because of the bug fixed in googleapis#4174 itself.
Closes#4167