Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

-1 On 6 February 2024 06:38:04 GMT, Bolke de Bruin wrote: >-1, binding. > > >Sent from my iPhone > >> On 5 Feb 2024, at 21:07, Scheffler Jens (XC-AS/EAE-ADA-T) >> wrote: >> >> +1 binding >> >> Sent from Outlook for iOS >> >> From:

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

-1, binding. Sent from my iPhone > On 5 Feb 2024, at 21:07, Scheffler Jens (XC-AS/EAE-ADA-T) > wrote: > > +1 binding > > Sent from Outlook for iOS > > From: Pankaj Koti > Sent: Monday, February 5, 2024 3:36:41 PM > To:

Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct

Let us try to summarise and see what the bot has to do. Summarising: 1. The bot should allow users to report issues - anonymously too (or maybe an option) 2. These issues should get redirected to an admin channel / private channel 3. Some command in the bot that could allow users to find out the

Re: Idea for Discussion: custom TI dependencies

Another thing to consider is whether TI deps is the right place for this kind of thing. The two examples were pretty infra related. Maybe it makes sense in those cases for the TI's scheduling deps to be cleared but then the executor needs to manage scaling up the infra for the task or

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

+1 binding Sent from Outlook for iOS From: Pankaj Koti Sent: Monday, February 5, 2024 3:36:41 PM To: dev@airflow.apache.org Subject: Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution +1 (binding) Best

Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct

I agree with the bot idea- does anyone on this thread have the ability to implement it? On Mon, Feb 5, 2024 at 8:58 AM Bishundeo, Rajeshwar wrote: > The bot idea is great and being able to be anonymous is important! I'm not > a fan of filling out forms and that could be a deterrent for people

[ANNOUNCE] January 2024 Airflow Monthly Newsletter

IF YOU WOULD LIKE TO SEE THE FORMATTED VERSION OF THE NEWSLETTER, PLEASE GO HERE Hey Team, This month in the Airflow Community, we rang in the New Year by introducing new programs, growing existing ones, and as always, maintaining a

Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct

The bot idea is great and being able to be anonymous is important! I'm not a fan of filling out forms and that could be a deterrent for people trying expressing their concerns, especially if they misinterpret the form structure/criteria. So def in favor of a #2 type approach with a bot. --

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

+1 (non-binding) from me based on my past comments on the thread. -- Regards, Aritra Basu On Mon, Feb 5, 2024, 8:07 PM Pankaj Koti wrote: > +1 (binding) > > > Best regards, > > *Pankaj Koti* > Senior Software Engineer (Airflow OSS Engineering team) > Location: Pune, Maharashtra, India >

Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct

I think the bot would be best. It would be great if the reports are made to a private channel (the bot that Andrey posted seems to be doing just that) where it can be discussed between the admin channels and action taken. Plus some way of knowing who is in the admin channel and invitation to

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

+1 (binding) Best regards, *Pankaj Koti* Senior Software Engineer (Airflow OSS Engineering team) Location: Pune, Maharashtra, India Timezone: Indian Standard Time (IST) Phone: +91 9730079985 On Mon, Feb 5, 2024 at 8:05 PM Amogh Desai wrote: > +1 from me too based on my earlier points. > >

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

+1 from me too based on my earlier points. Wondering if we can make it a little more rigid to address the concerns about hiding comments from the email thread earlier Thanks & Regards, Amogh Desai On Mon, Feb 5, 2024 at 7:47 PM Jarek Potiuk wrote: > Hello, > > We have been discussing and

Re: Idea for Discussion: custom TI dependencies

I had my answer drafted before Ash sent it so I will copy it here. But I very much agree with Ash's assessment. I did not realise we could do that with task_policy but if we can, then I would go for it - having it undocumented feature for power users. Making it a feature is a big task that would

[VOTE] "Require conversation resolution" setting in PRs as permanent solution

Hello, We have been discussing and arguing and it seems that we do not have a consensus of whether "require conversation resolution" is a good idea, as promised I am casting a VOTE on it. The discussion is in this thread: https://lists.apache.org/thread/bzg00p8yolboqgwlwfnlkdfvnn996601 Voting

Re: Idea for Discussion: custom TI dependencies

This is an absolute minefield of performance issues as this is the very centre of the hot path for the scheduler, so I would advise against any casual use of this. That said: I think it’s possible today. Set `deps` on your operator class like

AIP-59

Hello Airflow community! I'd like to announce an AIP related to Performance Testing Framework for Airflow. We've discussed such a need during Airflow Summit 2023 and we found it a useful ecosystem addition. The framework aims to collect various statistics in a manner that is decoupled from a