| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
The docs failure seems to be unrelated to the actual change, it was just revealed now that we re-generated the files from protos. |
Sorry, something went wrong.
|
Please prioritize - we use pipenv and this compatibility problem has broken our development flow |
Sorry, something went wrong.
|
@dhendry As of PubSub 1.4.3, the api-core dependency has been restricted to version < 1.17.0 and should not be experiencing this issue. Or is there another factor involved? 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! |
Sorry, something went wrong.
|
@plamut We ran into problems because the latest version google-api-python-client (1.9.1) requires "google-api-core>=1.17.0,<2dev", which is incompatible with the google-cloud-pubsub restriction of < 1.17.0 (see https://github.com/googleapis/google-api-python-client/blob/v1.9.1/setup.py#L44) For us google-api-python-client was being pulled in implicitly as a dependency of firebase-admin |
Sorry, something went wrong.
|
@dhendry Ah, understood. The pip resolver should not allow that to be installed, but it currently has some bugs. Anyhow, I will push for a new PubSub fix + release as soon as the api-core part of the fix is merged. |
Sorry, something went wrong.
|
@dhendry (and others) As a temporary workaround, would it be feasible to pin and install an older version of google-api-python-client that does not require api-core >=1.17.0? |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
|
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 api-core releases that do not have the required fix yet. We will have to update the api-core version pin when it's clear which version range should be excluded. |
Sorry, something went wrong.
|
@plamut The api-core PR is merged and just released (v1.20.0). |
Sorry, something went wrong.
|
We're going to try to get this in for release 1.6.0. |
Sorry, something went wrong.
|
@pradn Please just wait until I update version pins. Update: Done, 1.20.0 is the first api-core version that includes the other part of the fix. All others from 1.17.0 on are banned. |
Sorry, something went wrong.
There was a problem hiding this comment.
Perfect!
Sorry, something went wrong.
## [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))
| Back | FazBrowse Home | New Git URL |
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