-
Notifications
You must be signed in to change notification settings - Fork 96
fix: closes tailing streams in bidi classes. #851
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
Conversation
|
I think we'll need a similar change on the async side as well: https://github.com/chandra-siri/python-api-core/blob/82cea4f767510be2002fcc5807a770b99a2906c1/google/api_core/bidi_async.py#L198 |
pujawadare
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also included async bidi classes in the fix.
712e18a to
a585f25
Compare
7da01b3 to
6768183
Compare
6768183 to
93dff59
Compare
Always put `None` into the request queue when closing a bidi stream. This ensures that the request queue is always signaled as closed, even if the underlying gRPC call object is not yet available.
3ca7e57 to
695de92
Compare
chalmerlowe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Always put
Noneinto the request queue when closing a bidi stream. This ensures that the request queue is always signaled as closed, even if the underlying gRPC call object is not yet available.Fixes #850 🦕