Re: [DISCUSS] simplifying try_number handling

Looks good to me. Personally I never ran into any issues with this so far but I agree with the issues it solves. Thanks & Regards, Amogh Desai On Fri, May 3, 2024 at 2:50 AM Vincent Beck wrote: > I am all +1 on this one. This thing gave me headaches when working on > AIP-44 and I could not

Re: [VOTE] Release Airflow 2.9.1 from 2.9.1rc2

+1 non binding Performed the same tests as RC1 and found no issues. Installed the RC, ran a few DAGs from my tests, and random clicks on UI. Thanks & Regards, Amogh Desai On Fri, May 3, 2024 at 1:03 AM Ephraim Anierobi wrote: > Hey fellow Airflowers, > > I have cut Airflow 2.9.1rc2. This

Re: [DISCUSS] simplifying try_number handling

I am all +1 on this one. This thing gave me headaches when working on AIP-44 and I could not understand the difference between the private "_try_number" and the public "try_number". Thanks for simplifying it! This is obviously assuming it does not break anything I am not aware of :) On

[ANNOUNCE] Apache Airflow Python Client 2.9.0 Released

Dear Airflow community, I'm happy to announce that Apache Airflow Python Client 2.9.0 was just released. We made this version available on PyPI for convenience: `pip install apache-airflow-client` https://pypi.org/project/apache-airflow-client/2.9.0/ The documentation is available at:

[DISCUSS] simplifying try_number handling

TLDR * changing handling of try_number in https://github.com/apache/airflow/pull/39336 * no more private attr * no more getter that changes value based on state of task * no more decrementing * try number now only handled by scheduler * hope that sounds good to all of you For more detail read

[VOTE] Release Airflow 2.9.1 from 2.9.1rc2

Hey fellow Airflowers, I have cut Airflow 2.9.1rc2. This email is calling a vote on the release, which will last at least 30 hours, from Thursday, May 2, 2024 at 07:0 pm UTC until Saturday, May 4, 2024, at 01:30 am UTC

[RESULT][VOTE] Release Apache Airflow Python Client 2.9.0 from 2.9.0rc1

Hello, Apache Airflow Python Client 2.9.0 (based on RC1) has been accepted. 4 "+1" binding votes received: - Jed Cunningham - Jarek Potiuk - Kaxil Naik - Hussein Awala 2 "+1" non-binding votes received: - Pankaj Koti - Amogh Desai Vote thread:

Re: [VOTE] Release Airflow 2.9.1 from 2.9.1rc1

Hey fellow Airflowers, A bug was found in rc1 that'll necessitate an rc2. I'm canceling this vote and will create 2.9.1rc2 soon. - Ephraim On Thu, 2 May 2024 at 06:01, Amogh Desai wrote: > +1 non binding > > Did a general testing by installing the RC, ran a few DAGs, performed some > random

Re: [VOTE] Airflow Providers prepared on May 01, 2024

I will exclude pinecone from this release. Please continue voting excluding pinecone provider On Thu, May 2, 2024 at 3:19 PM Ankit Chaurasia wrote: > -1 non-binding for Pinecone: 2.0.0rc1 > > There is an issue with Pinecone: 2.0.0rc1 with the system test. This bug is > introduced as part of the

Re: [VOTE] Airflow Providers prepared on May 01, 2024

-1 non-binding for Pinecone: 2.0.0rc1 There is an issue with Pinecone: 2.0.0rc1 with the system test. This bug is introduced as part of the following PR Pinecone provider support for pinecone-client>=3 (#37307): @rawwar PR #39365