-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Status of testing Providers that were prepared on August 05, 2023 #33132
Comments
I can confirm that #33045 makes them default timeout sufficiently long. |
#32760 works on main branch (provider versions seem to match above). Could someone please tell me how to install specific provider versions in a breeze environment? I am having some trouble following the directions in https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#provider-packages |
See the link posted in the issue at the top Verify providers by contributors There are very precise instructions. UPDATE (but the link is not precise - pointing to old chapter - this is the right link :D https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors |
Checked all my changes - they all look good - except redis. I found out that the fix caused multiple "subscribe" calls for the sensor, so would likely cause problems. We should remove redis from the list, the fix for rc2 is coming. |
Tested mine changes, they look good. |
Tested my changes, they are included and they work as expected |
Tested my changes with https://pypi.org/project/apache-airflow-providers-amazon/8.5.0rc1/ |
Tested my minor changes worked well |
Tested my refactor on azure #32980 |
#32605 <#32605> work as expected
apache-airflow-providers-snowflake==4.4.1rc1
pon., 7 sie 2023 o 10:27 max ***@***.***> napisał(a):
… #32960 <#32960> and #32861
<#32861> work as expected
apache-airflow-providers-google==10.6.0rc1
apache-airflow-providers-celery==3.3.1rc1
apache-airflow-providers-amazon==8.5.0rc1
apache-airflow-providers-cncf-kubernetes==7.4.1rc1
—
Reply to this email directly, view it on GitHub
<#33132 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC7WCJL4VRGIH5TYC7ZJER3XUCRFPANCNFSM6AAAAAA3EXZR4Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thank you everyone. google and redis providers are excluded, I will cut RC2 shortly I invite everyone to help improve providers for the next release, a list of open issues can be found here. |
Body
I have a kind request for all the contributors to the latest provider packages release.
Could you please help us to test the RC versions of the providers?
Let us know in the comment, whether the issue is addressed.
Those are providers that require testing as there were some substantial changes introduced:
Provider amazon: 8.5.0rc1
waiter_max_attempts
for deferred BatchJobOperator (#33045): @rishi-kulkarniProvider apache.drill: 2.4.3rc1
Provider apache.hive: 6.1.4rc1
Provider apache.spark: 4.1.3rc1
Provider apache.sqoop: 4.0.0rc1
Provider asana: 2.2.2rc1
Provider celery: 3.3.1rc1
Provider cncf.kubernetes: 7.4.1rc1
xcom_sidecar
(#32858): @pegasasProvider common.sql: 1.6.2rc1
SQLExecuteQueryOperator
signature consistent with other SQL operators (#32974): @potiukProvider docker: 3.7.2rc1
Provider ftp: 3.5.0rc1
Provider google: 10.6.0rc1
Provider imap: 3.3.0rc1
ssl_context
extra for SMTP and IMAP connections (#33112): @potiukProvider microsoft.azure: 6.2.3rc1
Provider mysql: 5.2.1rc1
Provider openlineage: 1.0.1rc1
Provider redis: 3.3.1rc1
Provider smtp: 1.3.0rc1
ssl_context
extra for SMTP and IMAP connections (#33112): @potiukProvider snowflake: 4.4.1rc1
SnowflakeValueCheckOperator
(#32605): @frodo2000The guidelines on how to test providers can be found in
Verify providers by contributors
All users involved in the PRs:
@pankajkoti @moiseenkov @okayhooni @hankehly @frodo2000 @VladaZakharova @hussein-awala @mahammi @mobuchowski @kimdwkimdw @ephraimbuddy @potiuk @eumiro @pegasas @rishi-kulkarni @JDarDagran
Committer
The text was updated successfully, but these errors were encountered: