+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]
