Repository navigation
Status of testing Providers that were prepared on November 24, 2024 #44324
Description
Activity
Hi, #44053 works as expected.
Reacted by Elad Kalif#42810 is good.
Reacted by Elad Kalif#44214 is good
Reacted by Elad Kalif@eladkal So I verified that #43890 works with
apache-airflow>=2.10.0-
However, there's an error when I do the same with
apache-airflow==2.9.3-
Unless I am doing something wrong, in which case please let me know, it seems that this is happening because of #41021 which seems to be linked to the airflow 2.10.0 milestone. If that's the case, maybe we should update the documentation for it on PyPi?
Reacted by Elad Kalif and Jarek PotiukHowever, there's an error when I do the same with apache-airflow==2.9.3
Good catch. Apparently we miss compatibility class for that in "common.compat" and the sensor has no corresponding tests that would detect it in "providers/tests/standard/sensors" - the test for filesystem sensor is still in "tests/sensors" that's why our test suite did not catch it.
If that's the case, maybe we should update the documentation for it on PyPi?
Nope. We want to keep 2.8+ compatibility. We should add compatibilty
StartTriggerArgsclass in "common.compat" similarly to other "after 2.8" features, and import the class from there in the sensor.I guess @eladkal - since it's not a regression and standard provider is still 0.* it's not a blocker for the release and can be fixed as a follow-up.
@potiuk is correct, we don't consider this as a regression as standard provider is not yet "stable".
Specifically for 2.9.x the sensor is reachable by importing from core path. The PR in question just moved it from core to providers so while it doesn't work as intended there is simple workaround for 2.9@kunaljubce if you can raise a PR with a fix that would be much appreciated
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 celery: 3.8.5rc1
Provider cncf.kubernetes: 10.0.1rc1
Provider google: 11.0.0rc1
BigQueryAsyncHook.create_job_for_partition_get(#44225): @sean-roseLinked issues:
google-cloud-translateto3.16(#44297): @kaxilProvider standard: 0.0.2rc1
TriggerDagRunOperatorto standard provider (#44053): @hardeybiseyLinked issues:
Linked issues:
All users involved in the PRs:
@amirmor1 @dimberman @hardeybisey @fredthomsen @MaksYermak @sunank200 @kunaljubce @kacpermuda @sean-rose @kaxil @olegkachur-e @moiseenkov @gopidesupavan
Committer