-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Change retry type for Google Clients to async ones where needed #36141
Conversation
Needs few more libraries and more complete/selective use of AsyncRetry - seems the fixes were applied to a number of Google clients. |
c12c8c6
to
a43fbba
Compare
Right .. That one should be green (and I believe good for RC2 of google provider). |
a43fbba
to
0d0a25a
Compare
OK. I found one more edge case in the new "provider verification" a fix to that will follow - then we will be able to merge it when It is merged. The problem is that if we bump a provider version and current constraints do not have it, we will not be able to install those new providers with old constraints. But there is a way to fix it. |
Fix in #36143 |
0d0a25a
to
e446d75
Compare
Google Dataflow Client 0.8.6 implemented bugfix where retry type was changed to async. This caused our canary builds to fail. We change the client to Async now and bump min version of the client to 0.8.6.
e446d75
to
6c24a9f
Compare
The fix worked :). and even had a follow-up. Merging it. |
Google Dataflow Client 0.8.6 implemented bugfix where retry type was changed to async. This caused our canary builds to fail. We change the client to Async now and bump min version of the client to 0.8.6. (cherry picked from commit 8d0c5d9)
Google Dataflow Clientss, implemented bugfixes where retry type was changed to async where async was used:
This caused our canary builds to fail.
We changed all the places where retry is Async now and bumped min version of the clients:
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.