-
Notifications
You must be signed in to change notification settings - Fork 207
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
fix: PubSub incompatibility with api-core 1.17.0+ #103
Conversation
The docs failure seems to be unrelated to the actual change, it was just revealed now that we re-generated the files from protos. |
Please prioritize - we use pipenv and this compatibility problem has broken our development flow |
@dhendry As of PubSub 1.4.3, the In any case, in order for this fix to work, a change also needs to be done (and released) in api-core. The change got a preliminary approval, and is now just awaiting some related check. cc: @crwilcox Do you have free cycles to prioritize the check? Thanks! |
@plamut We ran into problems because the latest version google-api-python-client (1.9.1) requires For us |
@dhendry Ah, understood. The Anyhow, I will push for a new PubSub fix + release as soon as the |
@dhendry (and others) As a temporary workaround, would it be feasible to pin and install an older version of |
@pradn Another pair of eyes would be useful for the fix on the PubSub side. I also removed all non-relevant synth changes from the PR to avoid the docs check issue due to mis-indented generated docstrings. |
We need to wait with merging until the api-core PR is merged and released, otherwise this fix will have no effect. Even worse - it can install one of the more recent |
@plamut The api-core PR is merged and just released (v1.20.0). |
We're going to try to get this in for release 1.6.0. |
@pradn Please just wait until I update version pins. Update: Done, 1.20.0 is the first |
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.
Perfect!
## [1.6.0](https://www.github.com/googleapis/python-pubsub/compare/v1.5.0...v1.6.0) (2020-06-09) ### Features * Add flow control for message publishing ([#96](https://www.github.com/googleapis/python-pubsub/issues/96)) ([06085c4](https://www.github.com/googleapis/python-pubsub/commit/06085c4083b9dccdd50383257799904510bbf3a0)) ### Bug Fixes * Fix PubSub incompatibility with api-core 1.17.0+ ([#103](https://www.github.com/googleapis/python-pubsub/issues/103)) ([c02060f](https://www.github.com/googleapis/python-pubsub/commit/c02060fbbe6e2ca4664bee08d2de10665d41dc0b)) ### Documentation - Clarify that Schedulers shouldn't be used with multiple SubscriberClients ([#100](#100)) ([cf9e87c](cf9e87c)) - Fix update subscription/snapshot/topic samples ([#113](#113)) ([e62c38b](e62c38b)) ### Internal / Testing Changes - Re-generated service implementaton using synth: removed experimental notes from the RetryPolicy and filtering features in anticipation of GA, added DetachSubscription (experimental) ([#114](#114)) ([0132a46](0132a46)) - Incorporate will_accept() checks into publish() ([#108](#108)) ([6c7677e](6c7677e))
Fixes #93.
This PR fixes the bug introduced in api-core 1.17.0 that breaks streaming pull recovery on recoverable errors.
The fix depends on the related pull request in API core that allows disabling the automatic pre-fetch of the first stream result.
Probably best to not merge until a new
api-core
version is released, as the fix here will not have any effect on its own, and will not close the issue yet.cc: @pradn
PR checklist