Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python as_completed failed on gRPC futures #18611

Closed
yutkin opened this issue Apr 2, 2019 · 1 comment
Closed

Python as_completed failed on gRPC futures #18611

yutkin opened this issue Apr 2, 2019 · 1 comment

Comments

@yutkin
Copy link

yutkin commented Apr 2, 2019

What version of gRPC and what language are you using?

Python 3.6.8
grpcio 1.19.0
grpcio-tools 1.18.0

What operating system (Linux, Windows,...) and version?

Linux

What did you do?

Using Python concurrent.futures.as_completed for gRPC futures.

What did you see?

...
> File "service.py", line 284, in Handle
   for i in futures.as_completed(ff, timeout=5):
            │       │            └ [<_Rendezvous of RPC that terminated with:
            │       │              	status = StatusCode.OK
            │       │              	details = ""
            │       │              >, <_Rendezvous object of in-flight RPC>, <_Ren...
            │       └ <function as_completed at 0x7f66f6c4e268><module 'concurrent.futures' from '/usr/local/lib/python3.6/concurrent/futures/__init__.py'>
  File "/usr/local/lib/python3.6/concurrent/futures/_base.py", line 219, in as_completed
   with _AcquireFutures(fs):
        │               └ {<_Rendezvous object of in-flight RPC>, <_Rendezvous of RPC that terminated with:
        │                 	status = StatusCode.OKdetails = "">, <_Ren...
        └ <class 'concurrent.futures._base._AcquireFutures'>
 File "/usr/local/lib/python3.6/concurrent/futures/_base.py", line 146, in __enter__
   future._condition.acquire()
   └ <_Rendezvous object of in-flight RPC>
AttributeError: '_Rendezvous' object has no attribute '_condition'```
@stale
Copy link

stale bot commented Sep 29, 2019

This issue/PR has been automatically marked as stale because it has not had any update (including commits, comments, labels, milestones, etc) for 180 days. It will be closed automatically if no further update occurs in 1 day. Thank you for your contributions!

@stale stale bot closed this as completed Sep 30, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Dec 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants