Thank you all! Yes, it is starting to look like a lazy consensus candidate. :) Unless there are any objections today or tomorrow, I'll start that on Saturday (so Monday is in the window).
And sorry about the initial confusion I should have specified that I am only talking about a config default change in the tldr, that detail is a bit hidden in the text. On Thu, Mar 6, 2025 at 10:12 AM Ash Berlin-Taylor <[email protected]> wrote: > +1 — coupled with the ability to do backfills in the UI now, if there is > also want the old behaviour back on an ad-hoc basis it’s easy to get the > missing runs created too. > > -ash > > > On 5 Mar 2025, at 22:26, Jarek Potiuk <[email protected]> wrote: > > > > Looks like `[LAZY CONSENSUS]` candidate to me :) > > > > On Wed, Mar 5, 2025 at 11:23 PM Oliveira, Niko > <[email protected]> > > wrote: > > > >> +1 as well,l I've never liked the default on behaviour for this config. > >> > >> ________________________________ > >> From: Jens Scheffler <[email protected]> > >> Sent: Wednesday, March 5, 2025 12:54:05 PM > >> To: [email protected] > >> Subject: RE: [EXT] [DISCUSSION] Changing catchup_by_default from True to > >> False > >> > >> CAUTION: This email originated from outside of the organization. Do not > >> click links or open attachments unless you can confirm the sender and > know > >> the content is safe. > >> > >> > >> > >> AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur > externe. > >> Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne > pouvez > >> pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain > que > >> le contenu ne présente aucun risque. > >> > >> > >> > >> +1 - I would also favor this proposal. > >> > >> On 05.03.25 21:25, Akash Sharma wrote: > >>> +1 We should change it from both global and DAG level. > >>> > >>> Best regards, > >>> Akash > >>> > >>> On Thu, 6 Mar, 2025, 01:01 Jed Cunningham, <[email protected]> > >> wrote: > >>> > >>>> +1, this is one of the few configs that I change from the default > >>>> immediately. > >>>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
