Closed eladkal closed 9 months ago
https://github.com/apache/airflow/pull/35600 work :white_check_mark:
It has caused a problem with the example DAG (addressed in #35839) but the operator changes themselves work
35790 works
It has caused a problem with the example DAG (addressed in #35839) but the operator changes themselves work
Thanks. Since functionality work as expected this will not block rc1 release.
I tested https://github.com/apache/airflow/pull/35185 and https://github.com/apache/airflow/pull/35635, they work as expected.
Tested my set of PRs, all work fine, thank you for the release efforts!
I would like to see a re-discussion of https://github.com/apache/airflow/pull/32319 before including it.
I would like to see a re-discussion of #32319 before including it.
I think this is misunderstanding what #32319 wants to achieve. Commented there.
Conflirmed my template + reproducible builds worl (works great! PR shortly to a better PMC verification step is coming soon :) )
Tested my PR #35579 and it is working as expected.
We tested it with our example DAGs with apache-airflow-providers-amazon
, apache-airflow-providers-cncf-kubernetes
, apache-airflow-providers-databricks
, apache-airflow-providers-dbt-cloud
, apache-airflow-providers-google
, apache-airflow-providers-cncf-kubernetes
, apache-airflow-providers-microsoft-azure
, apache-airflow-providers-snowflake
and everything works as expected. Thanks!
https://github.com/apache/airflow/pull/35808 appears to be working as expected.
https://github.com/apache/airflow/pull/34840 works as expected.
https://github.com/apache/airflow/pull/35709 work as expected.
On Tue, 28 Nov 2023 at 00:14, Yoshiki Nagasaki @.***> wrote:
34785 https://github.com/apache/airflow/pull/34785 works as expected
— Reply to this email directly, view it on GitHub https://github.com/apache/airflow/issues/35845#issuecomment-1829119603, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQ3NQEZK57KWQF5RAV3UQQTYGVXKFAVCNFSM6AAAAAA7ZOR6K2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRZGEYTSNRQGM . You are receiving this because you were mentioned.Message ID: @.***>
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?
The guidelines on how to test providers can be found in
Verify providers by contributors
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.12.0rc1
check_key_async
is now in line with description of_check_key_async
(#35799): @bolleybollProvider apache.impala: 1.2.1rc1
Provider atlassian.jira: 2.3.0rc1
Provider cncf.kubernetes: 7.10.0rc1
Provider common.io: 1.1.0rc1
Provider common.sql: 1.8.1rc1
make_serializable
method (#32319): @Joffreybvnruff==0.0.292
changes in providers (#35053): @TaragolisProvider databricks: 5.0.1rc1
make_serializable
method (#32319): @JoffreybvnProvider dbt.cloud: 3.4.1rc1
Provider docker: 3.8.2rc1
Provider elasticsearch: 5.2.0rc1
Provider google: 10.12.0rc1
Provider microsoft.azure: 8.3.0rc1
Provider odbc: 4.2.0rc1
make_serializable
method (#32319): @JoffreybvnProvider openai: 1.0.1rc1
Provider opsgenie: 5.3.0rc1
OpsgenieNotifier
(#35530): @Eric-MendesProvider papermill: 3.5.0rc1
Provider redis: 3.4.1rc1
Provider snowflake: 5.1.2rc1
Provider trino: 5.4.1rc1
All users involved in the PRs: @ferruzzi @champon1020 @tskir @Eric-Mendes @pubudu91 @dashton90 @o-nikolas @raphaelauv @bolleyboll @ccorleis @MaksYermak @kacpermuda @uranusjr @akshaychitneni @dmedora @Joffreybvn @evgenyslab @ambika-garg @pankajkoti @potiuk @hussein-awala @ahzaz @tnyz @syedahsn @VladaZakharova @shohamy7 @austinletson @sseung00921 @dstandish @JDarDagran @bolkedebruin @vincbeck @ylnsnv @dirrao @Taragolis
Committer