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

"Thread-ConsumeBidirectionalStream caught unexpected exception 'generator' object has no attribute 'add_done_callback' and will exit." #670

Closed
mukund-ananthu opened this issue Jun 18, 2024 · 3 comments
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@mukund-ananthu
Copy link

Stacktrace:

"Thread-ConsumeBidirectionalStream caught unexpected exception 'generator'
object has no attribute 'add_done_callback' and will exit."

"Traceback (most recent call last):

File "/usr/local/lib/python3.8/site-packages/google/api_core/bidi.py", line
644, in _thread_main

self._bidi_rpc.open()

File "/usr/local/lib/python3.8/site-packages/google/api_core/bidi.py", line
294, in open

call._wrapped.add_done_callback(self._on_call_done)

AttributeError: 'generator' object has no attribute 'add_done_callback'"

Calling code: https://github.com/googleapis/python-pubsub/blob/509460520d6514361cc18675040b8b86a79d0271/google/cloud/pubsub_v1/subscriber/_protocol/streaming_pull_manager.py#L846-L854

Potentially similar issues: #309

Could you please let us know which scenarios could lead to the error and if this represents a bug ?

@vchudnov-g
Copy link
Contributor

Update: we're investigating and tracking internally (b/346537059) since this was triggered by an external report. When we have a status update relevant to this repo, we'll post it here.

@vchudnov-g vchudnov-g added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jun 24, 2024
@vchudnov-g
Copy link
Contributor

We resolved this internally; it seemed to be an issue with the customer code.

@IRusio
Copy link

IRusio commented Dec 13, 2024

@vchudnov-g how that was sorted out? we have that issue when we are using auto open telemetry instrumentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

4 participants