Yeah, it's easy to ignore messages from the cherry picker sometimes
assuming that adding PRs to the release milestone is good enough, but
more often than not the PR authors should ensure that their PRs land in the
right set of branches to avoid any surprises.
Thanks & Regards,
Amogh D
,
#53170,
#52978 and a CI fix: #53440.
Everything works as expected.
Thanks & Regards,
Amogh Desai
On Wed, Jul 30, 2025 at 5:16 PM Jarek Potiuk wrote:
> Kind request - to all PMC members - as I saw it a few times already). Can
> we please state what kind of verification we have don
Regards,
Amogh Desai
On Mon, Jul 28, 2025 at 12:37 AM Jens Scheffler
wrote:
> +1 from my side. Like the idea and also this does not people lead to
> think they can deploy via helm chart and run productive postgres.
>
> On 27.07.25 13:51, Aritra Basu wrote:
> > +1 to everythin
Nice to hear that opinion Ash, it's an interesting angle.
If someone works on a POC for that, would be interested to know how it
spans out.
Thanks & Regards,
Amogh Desai
On Mon, Jul 28, 2025 at 7:23 PM Ash Berlin-Taylor wrote:
> Yeah, I wasn’t sure if it would work for us. Let us
+1 for #49470, it is never easy to resolve such issues and it
was handled with patience and flair.
Kudos Jason!
Thanks & Regards,
Amogh Desai
On Tue, Jul 29, 2025 at 9:24 AM Aritra Basu
wrote:
> Same I believe for #46891, my vote would go for it. Conclusion of quite a
> l
valuable feedback and reviews.
Thanks & Regards,
Amogh Desai
27;),
call('Starting logging of task manager pod %s ',
'basic-example-taskmanager-1-1'),call("2022-09-25 19:01:47,027 INFO
KubernetesTaskExecutorRunner [] - ..."),call('Flink application ended
successfully')]*
Thanks & Regards,
Amogh Desai
On Fri, Jul 11
build up to fix the issues one package at a
time, and if
we can come up with a good AI prompt, we can get some work multiplexed by
the community
too.
Thanks & Regards,
Amogh Desai
On Thu, Jul 24, 2025 at 8:38 PM Jarek Potiuk wrote:
> Hello here,
>
> Since we have now started
Nice, so I think we have a quorum here!
Rich -- feel free to initiate something.
Thanks & Regards,
Amogh Desai
On Wed, Jul 23, 2025 at 10:23 PM Briana Okyere
wrote:
> Happy to join (if you all think it makes sense) to give a brief overview of
> our community initiatives like; meet
Hi Folks,
Just following up on this one…
Thanks & Regards,
Amogh Desai
On Fri, 18 Jul 2025 at 1:24 PM, Scheffler Jens (XC-AS/EAE-ADA-T)
wrote:
> If not too many persons already - would raise my hand as well. But three
> persons is already a good group.
>
> -Ursprün
+1 binding.
- Checked SVN
- Checked in Docker
- Checked reproducible package builds
- Checked licenses
- Checked Signatures
Used EdgeExecutor's integration test with some modifications to test
things, looks good.
Thanks & Regards,
Amogh Desai
On Fri, Jul 18, 2025 at 3:30 PM Kaxil Na
ther the coming
week sounds reasonable to me.
Mondays and Fridays are generally the days I have the most availability.
Thanks & Regards,
Amogh Desai
On Wed, Jul 16, 2025 at 8:57 AM Aritra Basu
wrote:
> This is pretty cool, I don't think I have much to add to the conversation
> y
it easier to follow the context.
Thanks & Regards,
Amogh Desai
On Wed, Jul 16, 2025 at 1:47 AM Jens Scheffler
wrote:
> Hi Jarek,
>
> cool! Thanks for all the efforts and the breath in preparing this! Added
> some comments in PR gut greatly appreciate (1) that notes desc
Good job folks!
You all have cranked so many PR's wow!
Thanks & Regards,
Amogh Desai
On Tue, Jul 15, 2025 at 12:28 PM Pavankumar Gopidesu <
gopidesupa...@gmail.com> wrote:
> Hi All, The cleanup process completed now, thanks everyone who helped make
> this possible.
&
That was a long one!!
Thanks to everyone who contributed to this release
Thanks & Regards,
Amogh Desai
On Tue, Jul 15, 2025 at 12:27 AM Kaxil Naik wrote:
> Dear Airflow community,
>
> I'm happy to announce that Airflow 3.0.3 was just released.
>
> The released sou
Amazing, it's good to see the bump happening!!
This is a great opportunity to learn how our static checks work too :)
Thanks & Regards,
Amogh Desai
On Sun, Jul 13, 2025 at 1:04 AM Jarek Potiuk wrote:
> Cool!
>
> On Sat, Jul 12, 2025 at 9:07 PM Pavankumar Gopidesu <
>
issue leading to this RC. Looking good!
Hopefully we can release it now!
Thanks & Regards,
Amogh Desai
On Sun, Jul 13, 2025 at 10:24 PM Hussein Awala wrote:
> +1 binding
>
> On Sunday, July 13, 2025, Ash Berlin-Taylor wrote:
>
> > +1 binding 🤞🏻
> >
> > -ash
Amazing!!
Thanks & Regards,
Amogh Desai
On Sun, Jul 13, 2025 at 10:33 PM Buğra Öztürk
wrote:
> Great news!
>
>
> On Sun, 13 Jul 2025, 19:58 Jarek Potiuk, wrote:
>
> > wooohoo!
> >
> > On Sun, Jul 13, 2025 at 5:48 PM Jed Cunningham >
> > wrote:
&
+1 binding.
Checked SVN, Reproducible Builds, Licenses and Signatures too.
Thanks & Regards,
Amogh Desai
On Sun, 13 Jul 2025 at 7:59 PM, Buğra Öztürk
wrote:
> +1 non-binding
>
> On Sun, 13 Jul 2025, 17:26 Jens Scheffler,
> wrote:
>
> > +1 (binding) - Checked SVN, R
Cool! Thanks for sharing your thoughts here Kevin, user perspective is
always important.
Thanks & Regards,
Amogh Desai
On Thu, Jul 10, 2025 at 6:59 PM Kevin Yang wrote:
> Hi, I joined airflow community around two months ago and I would also like
> to share some thoughts, probably m
_dag",
run_id="test_run",
task_id="pull_task",
map_index=-1,
),
)
for x in mock_supervisor_comms.send.call_args_list
)
call_args_list is particularly useful in scenarios when you want to
validate presence / absence of a call.
Th
/airflow/issues/52746#issuecomment-3055824279
and also general set of testing where I performed random UI clicks and ran
some tests with my
set of example dags. Looking good!
Thanks & Regards,
Amogh Desai
On Thu, Jul 10, 2025 at 2:17 AM Kaxil Naik wrote:
> Hey fellow Airflowers,
>
>
Agreed!
Once the PR is up, we can have these implementation level discussions
over there. Good chat however!
Thanks & Regards,
Amogh Desai
On Wed, Jul 9, 2025 at 3:56 PM Jarek Potiuk wrote:
> Yeah. I think extracting one-by-one, feature-by-feature that we want to
> share to
that would be better off in that "core_and_task_sdk" bundle.
Thanks & Regards,
Amogh Desai
On Tue, Jul 8, 2025 at 3:46 PM Jarek Potiuk wrote:
> > Not that I am against your idea and we can surely expand as we need but
> we would not need to expand the
> "core_a
+1 binding.
- Checked SVN
- Checked in Docker
- Checked reproducible package builds
- Checked licenses
- Checked Signatures
Installed the RC and checked if my cleanup code is present or not. It is
present and looks good!
Thanks & Regards,
Amogh Desai
On Wed, Jul 9, 2025 at 12:39 AM
be a good
candidate for that.
Not that I am against your idea and we can surely expand as we need but we
would not need to expand the
"core_and_task_sdk" if we put only the relevant items into it.
Thanks & Regards,
Amogh Desai
On Tue, Jul 8, 2025 at 12:28 PM Jarek Potiuk wrote:
ore please?
Naming is REALLY hard!
Thanks & Regards,
Amogh Desai
On Tue, Jul 8, 2025 at 2:52 AM Jarek Potiuk wrote:
> How about splitting it even more and having each shared "thing" named?
> "logging", "config" and sharing them explicitly and separately with t
/airflow-dag-builder
is one I remember from a couple of years ago.
Soon, there also will be multi language support for Airflow tasks and that
is also something
you can consider using if Python has a learning curve :)
Thanks & Regards,
Amogh Desai
On Tue, Jul 8, 2025 at 1:10 AM Jens Scheffler
w
27;d say you can either cast mocks to their types as one way:
`mock_http_run: MagicMock = mock_http_run` -- give or take, or use
`autospec` to make the mock reflect the signature of the object? Check out:
https://docs.python.org/3/library/unittest.mock.html#autospeccing
Thanks & Regards,
Amogh Des
time :). Easier said than done though!
Thanks & Regards,
Amogh Desai
On Mon, Jul 7, 2025 at 6:41 PM Jarek Potiuk wrote:
> > This might be related, or it might not be, but I think I would also love
> it if we moved all of “core” (scheduler, jobs, api server etc) to
> airflow_core.* pyt
,<4, especially in a big project
like ours where there are lot of newcomers
coming in all the time.
I am ok to go with whatever the community prefers here. I am more
interested in consistency in one way or another.
Thanks & Regards,
Amogh Desai
On Mon, Jul 7, 2025 at 3:22 PM Pavankuma
| 1
@sjyangkevin | 1
@kyungjunleeme | 1
Thanks & Regards,
Amogh Desai
On Mon, Jul 7, 2025 at 2:53 PM Jarek Potiuk wrote:
> Fantastic -> can you also share the image elsewhere - our devlist is not
> very good in getting embedded images through -> so all is is broken
er?): it's a more general
problem not due to the task but
similar / related to this
- Considering the worker backend angle
Thanks & Regards,
Amogh Desai
On Sun, Jul 6, 2025 at 11:39 PM Jarek Potiuk wrote:
> I think the only real "behavioural" change that you might expect from th
collaborate as a community.
Looking forward to more such collaborative efforts in the future!
Thanks & Regards,
Amogh Desai
On Thu, Jul 3, 2025 at 5:44 PM Amogh Desai wrote:
> Hello All,
>
> I recently moved `BaseHook` class into the task SDK:
> https://github.com/apache/airflow/pull/51
, tests work ok
#51957: fixing types better for dbt cloud connections, tests working fine
CI fixes:
#51916
#52214: version bump, all good
I also ran a couple of example dags from my test set and I do not see any
issue.
Thanks & Regards,
Amogh Desai
On Sat, Jul 5, 2025 at 2:32 AM Jarek Po
long as we have
a good CI workflow to probably
catch such issues per PR if changes are made in shared dist? (precommit
would make it really slow i guess)
If we can run our tests with vendored code we should be mostly covered.
Good effort all!
Thanks & Regards,
Amogh Desai
On Fri, Jul 4, 202
Hello All,
I recently moved `BaseHook` class into the task SDK:
https://github.com/apache/airflow/pull/51873. While I was doing this, we
were also running an effort to update `BaseOperator` imports in various
providers for AF3 compatibility which touched the version_compat.py and
created a nice im
processor / config etc etc as separate packages, back compat is going
to be a nightmare
and will bite us harder than we anticipate.
Thanks & Regards,
Amogh Desai
On Thu, Jul 3, 2025 at 1:12 AM Kaxil Naik wrote:
> I prefer Option 2 as well to avoid matrix of dependencies
>
> On Thu, 3 Jul
ve to fully
uncover and come up
with a detailed plan to allow this to be configurable.
Thanks & Regards,
Amogh Desai
On Wed, Jul 2, 2025 at 6:43 PM Jarek Potiuk wrote:
> I think this is a good idea - but as Ash mentioned, it has to be executed
> well with a lot of bells and whistles, so
to have the
ability to define multiple custom backends
both on worker or the API server.
Looking forward to hearing more from you.
Thanks & Regards,
Amogh Desai
On Wed, Jul 2, 2025 at 3:59 PM Anton Nitochkin
wrote:
> Hello,
>
> I'd like to discuss a new option that can be ad
Good job all. Appreciate all the effort, reviews, and design discussions
that went into it!
Good team work and this brings us closer to all providers using the task
SDK / AF 3 path :)
Thanks & Regards,
Amogh Desai
On Wed, Jul 2, 2025 at 5:42 AM Kevin Yang wrote:
> Thanks Kaxil,
>
As they say: "You may build a great product, but if it cannot be used by
people, it's garbage".
Thanks & Regards,
Amogh Desai
On Tue, Jul 1, 2025 at 1:08 PM Jarek Potiuk wrote:
> Woooho! Indeed .. Well done!
>
> Smart people I talk to in Open Source always told
👏 Congratulations Ankit.
Thanks & Regards,
Amogh Desai
On Tue, Jul 1, 2025 at 12:01 PM Ankit Chaurasia wrote:
> Thank you, everyone. The task-sdk docs are useful for users starting with
> it.
>
> *Ankit Chaurasia*
>
>
>
>
>
>
> On Tue, Jul 1, 2025 at 3:54
Vibe coding to the max!
I would love to try it out once too :D
Thanks & Regards,
Amogh Desai
On Sat, Jun 28, 2025 at 5:44 PM Jarek Potiuk wrote:
> This is super nice - and the super-detailed AI-centered instructions are
> extremely helpful - if you have access to some AI agen
Amazing Kaxil.
More work lead by the community strengthens the contributors base /
knowledge of the code base too.
Thanks for formulating this!
Thanks & Regards,
Amogh Desai
On Sat, 28 Jun 2025 at 11:44 AM, Jarek Potiuk wrote:
> Woooho !!! MORE Airflow 3 !
>
> On Sat, Jun
Good effort Elad.
I am sure it wasn't easy to maintain a green PR with all the changes coming
in into the repo continuously.
Well executed!
Thanks & Regards,
Amogh Desai
On Fri, Jun 27, 2025 at 6:57 PM Elad Kalif wrote:
> Dear Airflow Community,
>
> We have just dropped
. Thank you for believing in me and
welcoming me
into this role. I’m excited for what lies ahead, and I look forward to
continuing this journey with all of you.
Hoping to meet you all at the Airflow Summit. This year's celebratory cake
/ sweets will be from me!!
Thanks & Regards,
Amogh D
Torn between 51699 and 51735.
All tough ones this time!
Anyways, my vote would go to 51735, really good work. It's harder than it
looks!
(If i could give 2 plus ones, 51699 would get the other one)
Thanks & Regards,
Amogh Desai
On Thu, Jun 26, 2025 at 2:34 AM Briana Okyere
wrote:
providers from
using the DB! In case i come up with
something that involves / can use community help, I will make sure to reach
out.
Thanks for all you do, everyone!
Thanks & Regards,
Amogh Desai
On Fri, Jun 27, 2025 at 4:51 AM Jarek Potiuk wrote:
> This part of the cleanup is now complete.
+1 for this by all means!
I wonder if creating a GH board with work items (once we have them) would
help in
better tracking of the pending work
Thanks & Regards,
Amogh Desai
On Mon, Jun 23, 2025 at 2:57 AM Jarek Potiuk wrote:
> No need to +1 but ... yeah.. Supporting it by all means.
might not be the only
one we will implement in the long run. "human" operator sounds weird to me.
Thanks & Regards,
Amogh Desai
On Tue, Jun 24, 2025 at 1:43 PM Kaxil Naik wrote:
> Thanks Wei.
>
> 1) "Human in the Loop": +1 on the naming. Standard names. HI
Nice, good discussion!
Thanks & Regards,
Amogh Desai
On Wed, Jun 25, 2025 at 12:57 AM Jarek Potiuk wrote:
> PR here to add backport label automatically for dev tools changes (and to
> maintain it with minor version upgrades)
> https://github.com/apache/airflow/pull/52189
>
Right in time!
Thanks Jed and everyone involved!
Thanks & Regards,
Amogh Desai
On Tue, Jun 24, 2025 at 8:48 AM Jed Cunningham
wrote:
> Dear Airflow community,
>
> I am pleased to announce that we have released Apache Airflow Helm chart
> 1.17.0 🎉 🎊
>
> The source r
emove "airflow-core" from being a test dependency in those
> providers (and we will truly be able to see that indeed there are no
> left-overs in providers to follow our "airflow 3" architecture.
>
> J.
>
>
> On Mon, Jun 23, 2025 at 7:57 AM Amogh Desai
>
file2.py*
*We backport PR 1 as it's a bug fix and do not for PR 2 as its some
refactoring.*
*Now while trying to backport PR 3 (bugfix), it conflicts and needs PR 2 to
be picked*
*to land PR 3.*
Thanks & Regards,
Amogh Desai
On Mon, Jun 23, 2025 at 5:02 PM Ash Berlin-Taylor wrote:
, just for convenience sake.
Thanks & Regards,
Amogh Desai
On Fri, Jun 20, 2025 at 2:47 PM Jarek Potiuk wrote:
> Hey here,
>
> Over the last few days and weeks I made significant progress with Python
> 3.13 support and while the PR is not yet fully green - we are getting
> close
+1 non binding.
Installed the helm chart in a local minikube cluster and was able to run
airflow 3.0.2 without any issues. Ran a few example dags and played around
a bit on the UI with port forwarding, seems ok.
Thanks & Regards,
Amogh Desai
On Mon, Jun 23, 2025 at 9:47 AM Vishnu Chiluk
ress similar usage in system tests.
- Possibly improve the fixture to support adding multiple connections at
once.
- Update the Telegram provider tests (
*providers/telegram/tests/unit/telegram/hooks/test_telegram.py*).
Thanks & Regards,
Amogh Desai
On Sun, Jun 22, 2025 at 6:37
seems odd
that it is not descriptive enough
or doesn't highlight the intention of the operator enough.
I do not have concerns with whatever we decide to name it :D
Thanks & Regards,
Amogh Desai
On Mon, Jun 23, 2025 at 9:42 AM Jarek Potiuk wrote:
> In standard Provider, yes
>
> R
+1 non binding.
I didn't have any changes this time, but I had raised an issue
which seems to have been fixed.
Also installed the bits with AF 3.0.2 and verified user creation in FAB, no
issues.
Thanks & Regards,
Amogh Desai
On Sat, Jun 21, 2025 at 12:02 PM Shahar Epstein wrote:
Airflow. Waiting till the last day could also
lead to surprises
which might give us a hard time.
Thanks & Regards,
Amogh Desai
On Sun, Jun 22, 2025 at 3:20 PM Jarek Potiuk wrote:
> +1. We have more and more problems because some of our dependencies are
> already dropping support f
/apache/airflow/pull/50869 (after 2.11 release, compat
issue)
Actual changes:
1. https://github.com/apache/airflow/pull/51734
Thanks & Regards,
Amogh Desai
On Sun, Jun 15, 2025 at 6:28 PM Jens Scheffler
wrote:
> +1 (binding) - Checked SVN, Check in Docker, Reproducible package build,
>
+1 no objections!
Thanks & Regards,
Amogh Desai
On Sun, Jun 15, 2025 at 9:08 AM GUAN-MING CHIU
wrote:
> +1 non-binding
>
>
> On Sun, Jun 15, 2025 at 9:35 AM Wei Lee wrote:
>
> > +1
> >
> > > On Jun 14, 2025, at 10:43 PM, Jarek Potiuk wrote:
> >
+1 too.
Good work all of you!
Thanks & Regards,
Amogh Desai
On Sun, Jun 15, 2025 at 12:53 AM Shahar Epstein wrote:
> +1, great job everyone!
>
> Shahar
>
> On Sat, Jun 14, 2025 at 4:28 PM Wei Lee wrote:
>
> > Hi fellow Airflowers,
> >
> > Followi
This release looked small but has tons of bug fixes and CI stability fixes.
Good work as usual to everyone
who helped in contributing to the release! 👏
Thanks & Regards,
Amogh Desai
On Tue, Jun 10, 2025 at 8:39 PM Kaxil Naik wrote:
> Dear Airflow community,
>
> I'm happ
Amazing!
Thanks for this!
Thanks & Regards,
Amogh Desai
On Mon, Jun 9, 2025 at 5:03 PM Kaxil Naik wrote:
> Awesome, thanks Jarek
>
> On Sun, 8 Jun 2025 at 03:13, Jarek Potiuk wrote:
>
> > Dear Airflow community,
> >
> > I'm happy to announce that new
@Jarek Potiuk I agree with you. We should have a
separate doc for task sdk related verification and testing
sometime. Not urgent, but we can try to get that in by next release.
Thanks & Regards,
Amogh Desai
On Mon, Jun 9, 2025 at 11:49 AM Amogh Desai
wrote:
> +1 non binding.
>
>
Thanks & Regards,
Amogh Desai
On Sun, Jun 8, 2025 at 4:37 AM Jarek Potiuk wrote:
> +1 (binding)
>
> Checked my changes, reproducibility, signatures, checksums, I ran it
> locally. All looks good. The important "user facing" part I was quite
> involved in and added te
+1 binding.
Left some comments on the AIP, no major concerns, just some thoughts.
I am not a huge fan of using "human" as discussed above, so maybe having a
set of "interactive" operators makes sense?
Thanks & Regards,
Amogh Desai
On Thu, Jun 5, 2025 at 11:48 AM
+1 binding - well thought out document.
Thanks & Regards,
Amogh Desai
On Thu, Jun 5, 2025 at 2:04 AM Ahmad Farhan
wrote:
> As a native Arabic speaker, I am happy to review its translation once its
> PR is ready!
>
>
> On Wed, 4 Jun 2025 at 9:18 pm, Aritra Basu
> wrote
Thanks for starting the thread Shahar!
Well put up and far better than email discussions!
Thanks & Regards,
Amogh Desai
On Sun, Jun 1, 2025 at 7:59 PM Jens Scheffler
wrote:
> Hi all,
>
> thanks @shahar for posting the discussion and the document. First hand
> also added a few
Nice!
Thanks & Regards,
Amogh Desai
On Sat, May 31, 2025 at 4:30 PM Jarek Potiuk wrote:
> And another small follow-up before we release 3.0.2 as Jed pointed out in
> the previous PR, those example dags from standard provider do not really
> fit the same pattern as system tests +
/40975,
with a good amount of
analysis already done. Maybe you can get some data here that will be useful.
Thanks & Regards,
Amogh Desai
On Fri, May 30, 2025 at 9:27 PM Avi wrote:
> Hi All,
>
> Had a chat with @Kaxil. And we discussed on use-case first approach rather
> than o
My vote too goes for 50626, massive effort and an important one too!
Special shoutout to 50141 and 50964, lot of work put in and with great
quality too!
Thanks & Regards,
Amogh Desai
On Fri, May 30, 2025 at 8:55 AM Chia-Ping Tsai wrote:
> +1 to 50626 as it creates a more we
implementations of trying
to integrate Airflow officially / unofficially with an MCP server.
Thanks & Regards,
Amogh Desai
On Thu, May 29, 2025 at 2:56 AM Aaron Dantley
wrote:
> Hey!
>
> I also think this is a great idea!
>
> Would it be possible to be included in the development pro
If the user doesn't get to see the name directly as part of the interface,
deadline.expiration or deadline.deadline_time doesn't
bother me as much.
Somehow I like `deadline.deadline_time` better, that said, I am ok with
either as long as we document it well :)
Thanks & Regard
Looks good!
Thanks & Regards,
Amogh Desai
On Sat, May 24, 2025 at 5:15 AM Kaxil Naik wrote:
> Removed the old executor path too:
> https://github.com/apache/airflow/pull/51009
>
> On Fri, 23 May 2025 at 15:32, Pavankumar Gopidesu >
> wrote:
>
> > Nice thanks
Damn nice!
Lesser headache of fixing "two" ways of doing things!
Thanks & Regards,
Amogh Desai
On Fri, May 23, 2025 at 2:22 AM Jarek Potiuk wrote:
> Cool!
>
> On Thu, May 22, 2025 at 8:19 PM Kaxil Naik wrote:
>
> > Hey team,
> >
> > Happy to anno
quot;short
forms" like DAGs,
XComs, etc should be kept as-is imo.
Thanks & Regards,
Amogh Desai
On Fri, May 23, 2025 at 2:32 AM Tzu-ping Chung
wrote:
> The problem is, the line whether a term is technical or not is blurry at
> best.
>
> Dag—sure
> XCom—yeah
> Asset—pro
be some of the thoughts I have in mind.
I really like the idea and the inputs from others here and I would love to
join the party for this.
Thanks & Regards,
Amogh Desai
On Wed, May 21, 2025 at 10:07 AM Avi wrote:
> +1 for the opt-in feature. Can clearly see the need for this to exist
Thanks & Regards,
Amogh Desai
On Tue, May 20, 2025 at 2:40 PM Kaxil Naik wrote:
> Dear Airflow community,
>
> I'm happy to announce that Airflow 2.11.0 was just released.
>
> The released sources and packages can be downloaded via
>
> https://airflow.
+1 non binding.
Checked the changes, they look fine.
Thanks & Regards,
Amogh Desai
On Tue, May 20, 2025 at 3:47 PM Kaxil Naik wrote:
> +1 binding : checked signature & license
>
> On Tue, 20 May 2025 at 15:27, Elad Kalif wrote:
>
> > Hey all,
> >
> >
Amazing work, Jarek!
Watermark is nice too!
Thanks & Regards,
Amogh Desai
On Sat, May 17, 2025 at 2:07 AM Buğra Öztürk
wrote:
> Thanks Jarek! Amazing news!
> I like the watermark as well, it is a clear distinction :)
>
> On Fri, 16 May 2025, 14:13 Rahul Vats, wrote:
>
+1 non binding.
Ran a few example dags from my test suite, and performed a few clicks on the
UI doing various things. (Using the old UI now seems hard!)
Wei, your issue seems to be localised to SQLite.
Thanks & Regards,
Amogh Desai
On Sun, May 18, 2025 at 2:34 PM Jens Scheffler
wrote:
- Adding deprecation notice for get_current_context in std provider #50301
is for deprecation, works as expected. I see the deprecation there.
Thanks & Regards,
Amogh Desai
On Wed, May 14, 2025 at 5:42 PM Elad Kalif wrote:
> Hey all,
>
> I have just cut the new wave Airflow Providers p
Thank you Kaxil.
It is helpful for contributors to understand things too and for prevent
committers
from accidentally merging such PRs as we work on a precommit / CI test that
can avoid this trouble.
Thanks & Regards,
Amogh Desai
On Thu, May 15, 2025 at 10:35 AM Pavankumar Gopi
Superb news! Right on time!
Thanks to everyone who helped in fixing issues.
Thanks & Regards,
Amogh Desai
On Mon, May 12, 2025 at 5:32 PM Kaxil Naik wrote:
> Dear Airflow community,
>
> I'm happy to announce that Airflow 3.0.1 was just released.
>
> The released sou
Sounds great Jens, thanks for creating the channel and
thanks for updating us on it.
Thanks & Regards,
Amogh Desai
On Sun, May 11, 2025 at 7:54 PM Jens Scheffler
wrote:
> Hi,
>
> following-up on the discussion we had and the verbal discussion in
> Airflow 3 Dev call May 22
+1 non binding.
Installed the rc, ran some example dags with breeze. All good from my end
👍
Thanks & Regards,
Amogh Desai
On Mon, 12 May 2025 at 10:29 AM, Rahul Vats wrote:
> +1(Non-binding), verified running regression DAGs, and all work well.
>
>
> Regards,
> Rahul Vats
Superb!
Happy to see Constance vs Constrance :)
Thanks & Regards,
Amogh Desai
On Sat, May 10, 2025 at 12:14 AM Vikram Koka
wrote:
> That's awesome.
> Docs are critically important and shoutout to Constance for all the hard
> work on those!
>
> Vikram
>
> O
Excellent work Kaxil.
It was a pleasure reviewing the code. Well executed.
Thanks & Regards,
Amogh Desai
On Sat, May 10, 2025 at 10:17 AM Rahul Vats wrote:
> This is great! Thank you, Kaxil.
>
> Regards,
> Rahul Vats
>
> On Sat, 10 May 2025 at 10:14, Pavankum
Awesome one Pavan and the team who was involved.
The airflow-site repo checkout was a nightmare for sure! I hope to be
able to open it more happily and with my IDE not crashing :D
Thanks & Regards,
Amogh Desai
On Fri, May 9, 2025 at 2:39 PM Kaxil Naik wrote:
> Great work, Pavan in
Great effort on the docs.
+1 to https://github.com/apache/airflow/pull/49532 and
https://github.com/apache/airflow/pull/49468
Thanks & Regards,
Amogh Desai
On Fri, May 9, 2025 at 1:21 AM Pankaj Koti
wrote:
> +1 to https://github.com/apache/airflow/pull/49532
>
> Looks like
+1 non binding.
This time my changes were around CI fixes, those are indeed present and
it looks good.
Thanks & Regards,
Amogh Desai
On Fri, May 9, 2025 at 3:04 AM Jarek Potiuk wrote:
> +1 binding. Checked reproducibility, signatures, checksums, licences,
> checked that pa
Amazing. Thanks Jarek!
Thanks & Regards,
Amogh Desai
On Fri, May 9, 2025 at 2:49 AM Jarek Potiuk wrote:
> Hello here,
>
> Good news.
>
> I have just rebuilt images for Airflow 3.0.1 with the latest constraints -
> which include common-messaging == 1.0.1rc1 and amazon ==
I am sure it would have been a big challenge to identify the candidates
this time with so
many PRs coming this time.
Although, just wondering if we missed any with the #protm labels? Like, I
can recall this one
at least: https://github.com/apache/airflow/pull/48528
Thanks & Regards,
Amogh D
I would also be for bumping the minimum python version to 3.9+ for Airflow
3.1 unless
there is some objection to this one.
Maybe we should add this as a discussion item for the Airflow dev call?
Thanks & Regards,
Amogh Desai
On Thu, May 8, 2025 at 11:09 AM Jarek Potiuk wrote:
> I w
👏. Good problems to have!
Thanks & Regards,
Amogh Desai
On Wed, 7 May 2025 at 2:40 PM, Jarek Potiuk wrote:
> I had helped Briana to generate candidates for PR of the month for April
> and it run for many many minutes and ended up with 'reached 750 issues -
> giving u
Thanks Kaxil!
242 issues is really impressive :D
Thanks & Regards,
Amogh Desai
On Wed, May 7, 2025 at 3:56 AM Vikram Koka
wrote:
> Thanks Kaxil, 242 issues closed in this patch release!
> That's amazing!
>
> Vikram
>
>
>
> On Tue, May 6, 2025 at 2:49 PM Kaxil
could
be misled by mixed or outdated imports.
Thanks & Regards,
Amogh Desai
On Mon, May 5, 2025 at 6:28 PM Jarek Potiuk wrote:
> Following the question of the user here:
>
> https://apache-airflow.slack.com/archives/CCQ7EGB1P/p1746442613931879?thread_ts=1746430604.330269&cid=CCQ
1 - 100 of 431 matches
Mail list logo
