Congratulation Karthikeyan and Jeongwoo :) Thank you Kaxil for this shoutout as their work can set an example or inspiration to do such contributions among the community.
Regards, Bowrna On Fri, Oct 31, 2025 at 10:13 AM Ramasamy R <[email protected]> wrote: > Good work guys... > > On Fri, Oct 31, 2025 at 9:29 AM Rahul Vats <[email protected]> wrote: > > > Awesome job, guys -- huge shout-out to both of you! > > > > Regards, > > Rahul Vats > > > > On Fri, 31 Oct 2025 at 09:22, Amogh Desai <[email protected]> wrote: > > > > > Kudos, Karthikeyan and Jeongwoo! > > > > > > We often underestimate how important it is to create issues with enough > > > detail > > > and steps to repro the situation which can avoid a lot of cycles for > > > maintainers & > > > other contributors to triage and fix the issues too. > > > > > > We should do such shoutouts more often, thanks for setting this > example, > > > Kaxil! > > > > > > > > > Thanks & Regards, > > > Amogh Desai > > > > > > > > > On Fri, Oct 31, 2025 at 4:40 AM Vikram Koka via dev < > > > [email protected]> > > > wrote: > > > > > > > +1 to that. > > > > > > > > Thanks for highlighting this, Kaxil. > > > > I had seen the work from Karthikeyan and had highlighted that on the > > 3.x > > > > wiki page < > > > https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.x > > > > >, > > > > but I hadn't seen the work from Jeongwoo. > > > > > > > > Kudos to both of you, Karthikeyan and Jeongwoo. Great job! > > > > > > > > > > > > > > > > On Thu, Oct 30, 2025 at 1:37 PM Ryan Hatter via dev < > > > > [email protected]> > > > > wrote: > > > > > > > > > Great callout, Kaxil. This kind of work is hugely important and > often > > > > > overlooked! Well done Karthikeyan and Jeongwoo. > > > > > > > > > > On Thu, Oct 30, 2025 at 11:54 AM Jarek Potiuk <[email protected]> > > > wrote: > > > > > > > > > > > Indeed. A big shoutout to both. > > > > > > > > > > > > On Thu, Oct 30, 2025 at 4:42 PM Pierre Jeambrun < > > > [email protected] > > > > > > > > > > > wrote: > > > > > > > > > > > > > Great work to both of you, that's super helpful! > > > > > > > > > > > > > > On Thu, Oct 30, 2025 at 3:23 PM Vincent Beck < > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > > > +1 to that. Discovering bugs and filling out a well described > > > issue > > > > > is > > > > > > so > > > > > > > > much important. Especially in a project like Airflow where > > > thinking > > > > > and > > > > > > > > testing all different scenarios, environment, etc is nearly > > > > > impossible. > > > > > > > > Thank you guys! > > > > > > > > > > > > > > > > On 2025/10/30 13:39:27 Kaxil Naik wrote: > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > > > We have been running “PR of the Month” votes for a while > now > > > but > > > > > I’d > > > > > > > like > > > > > > > > > to take a moment to personally recognize two individuals > who > > > have > > > > > > gone > > > > > > > > > above and beyond in helping ensure the stability of Airflow > > > > 3.1.x. > > > > > > > > > > > > > > > > > > *Karthikeyan Singaravelan (tirkathi):* > > > > > > > > > > > > > > > > > > Karthikeyan has created more than 25 detailed GitHub issues > > > > > > > > > < > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/airflow/issues?q=is%3Aissue%20author%3Atirkarthi > > > > > > > > >, > > > > > > > > > many of which make fixing bugs significantly easier thanks > to > > > the > > > > > > > clarity > > > > > > > > > and completeness of his reports. > > > > > > > > > > > > > > > > > > In the last three weeks alone, he’s uncovered several > > critical > > > > > > issues, > > > > > > > > > including: > > > > > > > > > - N+1 query problems in the API server > > > > > > > > > - Scheduler/DAG Processor crashes under specific conditions > > > > > > > > > > > > > > > > > > *Jeongwoo Do (wjddn279):* > > > > > > > > > > > > > > > > > > While Jeongwoo has opened only a couple of GitHub issues > > > > > > > > > < > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/airflow/issues?q=is%3Aissue%20author%3Awjddn279> > > > > > > > > > recently, > > > > > > > > > it has had outsized impact. > > > > > > > > > The deep investigation into memory profiling and leaks > > directly > > > > > > > > contributed > > > > > > > > > to identifying and fixing the memory leak issues in Airflow > > > 3.1.1 > > > > > > > > > < > > > > > > > > > > > > https://github.com/apache/airflow/issues/56641#issuecomment-3461512931 > > > > > > > > >. > > > > > > > > > > > > > > > > > > The level of detail in the issue including steps to > reproduce > > > and > > > > > > > > > root-cause analysis made debugging far easier and was, in > > many > > > > > ways, > > > > > > as > > > > > > > > > valuable as the fixes themselves. > > > > > > > > > > > > > > > > > > A huge thank you to both Karthikeyan and Jeongwoo for doing > > > this. > > > > > > > > > > > > > > > > > > Contributions like these, even beyond code, play a major > role > > > in > > > > > > making > > > > > > > > > Airflow more stable and robust for everyone. > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > Kaxil > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Thanks & Regards > Ramasamy R > -- Regards Bowrna Prabhakaran
