dev  

Messages by Thread

• Apache - GSOC'25 projects / Contributions D. Mohith Akshay
  • Re: Apache - GSOC'25 projects / Contributions Bishundeo, Rajeshwar
  • Re: Apache - GSOC'25 projects / Contributions Ryan Hatter
• Two Hard Things: Deadline Alerts Edition Ferruzzi, Dennis
  • Re: Two Hard Things: Deadline Alerts Edition Jarek Potiuk
  • Re: Two Hard Things: Deadline Alerts Edition Tzu-ping Chung
  • Re: Two Hard Things: Deadline Alerts Edition Vincent Beck
  • Re: Two Hard Things: Deadline Alerts Edition Akash Sharma
  • Re: Two Hard Things: Deadline Alerts Edition Mehta, Shubham
  • Re: Two Hard Things: Deadline Alerts Edition Jarek Potiuk
  • Re: Two Hard Things: Deadline Alerts Edition Ferruzzi, Dennis
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Wei Lee
  • Re: Two Hard Things: Deadline Alerts Edition Amogh Desai
  • Re: Two Hard Things: Deadline Alerts Edition Pavankumar Gopidesu
  • Re: Two Hard Things: Deadline Alerts Edition Ankit Chaurasia
  • Re: Two Hard Things: Deadline Alerts Edition Ash Berlin-Taylor
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Jarek Potiuk
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Ferruzzi, Dennis
• [Meeting Notes] Airflow 3.0 dev call - 20 Feb 2025 Vikram Koka
  • Re: [Meeting Notes] Airflow 3.0 dev call - 20 Feb 2025 Amogh Desai
• [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Jarek Potiuk
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Jarek Potiuk
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
  • Re: [DISCUSS] New Provider for Gremlin Jarek Potiuk
  • Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
  • Re: [DISCUSS] New Provider for Gremlin Jarek Potiuk
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Paul King
  • Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • RE: Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
• [VOTE] Airflow Providers prepared on February 21, 2025 Elad Kalif
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Jens Scheffler
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Oliveira, Niko
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Amogh Desai
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Jarek Potiuk
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Vishnu Chilukoori
• [DISCUSS] Proposal to enhance the PR template Amogh Desai
  • Re: [DISCUSS] Proposal to enhance the PR template Ankit Chaurasia
  • Re: [DISCUSS] Proposal to enhance the PR template Daniel Standish
  • Re: [DISCUSS] Proposal to enhance the PR template Daniel Standish
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
  • Re: [DISCUSS] Proposal to enhance the PR template Wei Lee
  • Re: [DISCUSS] Proposal to enhance the PR template Amogh Desai
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
  • Re: [DISCUSS] Proposal to enhance the PR template Ferruzzi, Dennis
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
  • Re: [DISCUSS] Proposal to enhance the PR template Ferruzzi, Dennis
  • Re: [DISCUSS] Proposal to enhance the PR template Ferruzzi, Dennis
  • Re: [DISCUSS] Proposal to enhance the PR template Amogh Desai
  • Re: [DISCUSS] Proposal to enhance the PR template Ferruzzi, Dennis
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
• 📢 Apache Airflow 3.0.0apha4 is available for testing! 🎉 Jed Cunningham
  • Re: 📢 Apache Airflow 3.0.0apha4 is available for testing! 🎉 Vikram Koka
• [REMINDER]: Airflow 3 Dev call on 20th February - agenda Vikram Koka
  • Re: [REMINDER]: Airflow 3 Dev call on 20th February - agenda Jarek Potiuk
• [DISCUSS] Python 3.13 support Jarek Potiuk
  • Re: [DISCUSS] Python 3.13 support Jarek Potiuk
  • RE: [DISCUSS] Python 3.13 support Damian Shaw
  • Re: [DISCUSS] Python 3.13 support Tzu-ping Chung
  • RE: [DISCUSS] Python 3.13 support Damian Shaw
  • Re: [DISCUSS] Python 3.13 support Jarek Potiuk
  • Re: [DISCUSS] Python 3.13 support Jarek Potiuk
• [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jarek Potiuk
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jarek Potiuk
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Daniel Standish
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jed Cunningham
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jens Scheffler
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jarek Potiuk
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Buğra Öztürk
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jarek Potiuk
• [DISCUSS] Time to say goodbye to the old UI? Jed Cunningham
  • Re: [DISCUSS] Time to say goodbye to the old UI? Wei Lee
  • Re: [DISCUSS] Time to say goodbye to the old UI? Amogh Desai
  • Re: [DISCUSS] Time to say goodbye to the old UI? Shubham Raj
  • Re: [DISCUSS] Time to say goodbye to the old UI? Rahul Vats
  • Re: [DISCUSS] Time to say goodbye to the old UI? Ankit Chaurasia
  • Re: [DISCUSS] Time to say goodbye to the old UI? Abhishek Bhakat
  • Re: [DISCUSS] Time to say goodbye to the old UI? Michał Modras
  • Re: [DISCUSS] Time to say goodbye to the old UI? Ash Berlin-Taylor
  • Re: [DISCUSS] Time to say goodbye to the old UI? Michał Modras
  • Re: [DISCUSS] Time to say goodbye to the old UI? Abhishek Bhakat
  • Re: [DISCUSS] Time to say goodbye to the old UI? Jed Cunningham
  • Re: [DISCUSS] Time to say goodbye to the old UI? Vincent Beck
  • Re: [DISCUSS] Time to say goodbye to the old UI? Vikram Koka
  • Re: [DISCUSS] Time to say goodbye to the old UI? Kaxil Naik
  • Re: [DISCUSS] Time to say goodbye to the old UI? Karthikeyan
  • Re: [DISCUSS] Time to say goodbye to the old UI? Ferruzzi, Dennis
  • Re: [DISCUSS] Time to say goodbye to the old UI? Brent Bovenzi
  • Re: [DISCUSS] Time to say goodbye to the old UI? Brent Bovenzi
  • Re: [DISCUSS] Time to say goodbye to the old UI? Jarek Potiuk
  • Re: [DISCUSS] Time to say goodbye to the old UI? Buğra Öztürk
  • Re: [DISCUSS] Time to say goodbye to the old UI? Pavankumar Gopidesu
  • Re: [DISCUSS] Time to say goodbye to the old UI? Jed Cunningham
  • Re: [DISCUSS] Time to say goodbye to the old UI? Jarek Potiuk
  • Re: [DISCUSS] Time to say goodbye to the old UI? Constance Martineau
• [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Alexander Shorin
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Vincent Beck
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Amogh Desai
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ash Berlin-Taylor
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ash Berlin-Taylor
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ash Berlin-Taylor
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ash Berlin-Taylor
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ferruzzi, Dennis
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Oliveira, Niko
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Vincent Beck
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jens Scheffler
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jens Scheffler
• [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Aritra Basu
  • Re: [DISCUSS] Tests structure for providers Jens Scheffler
  • Re: [DISCUSS] Tests structure for providers Ash Berlin-Taylor
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Ash Berlin-Taylor
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Rahul Vats
  • Re: [DISCUSS] Tests structure for providers Buğra Öztürk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Buğra Öztürk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Ferruzzi, Dennis
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Ferruzzi, Dennis
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Ferruzzi, Dennis
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
• [DISCUSS] Next steps in provider's sub-projects separation Jarek Potiuk
• [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Constance Martineau
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jens Scheffler
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jarek Potiuk
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jens Scheffler
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jarek Potiuk
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jed Cunningham
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jens Scheffler
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Amogh Desai
• 📢 Apache Airflow 3.0.0alpha3 is available for testing! 🎉 Utkarsh Sharma
  • Re: 📢 Apache Airflow 3.0.0alpha3 is available for testing! 🎉 Vikram Koka
  • Re: 📢 Apache Airflow 3.0.0alpha3 is available for testing! 🎉 Jarek Potiuk
  • Re: 📢 Apache Airflow 3.0.0alpha3 is available for testing! 🎉 Amogh Desai
• [DISCUSS]: Proposing a "common message queue" abstraction Vikram Koka
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Wei Lee
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Abhishek Bhakat
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Ben Tallman
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Jarek Potiuk
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Jens Scheffler
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Vikram Koka
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Igor Kholopov
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Amogh Desai
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Mehta, Shubham
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Vishnu Chilukoori
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Ankit Chaurasia
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Mehta, Shubham
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Vincent Beck
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Pierre Jeambrun
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Constance Martineau
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Ephraim Anierobi
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Rahul Vats
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Idris Adebisi
• Updating "zombie task" terminology to "task heartbeat timeout" Karen Braganza
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Ryan Hatter
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Wei Lee
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" kalyan reddy
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Jarek Potiuk

• Earlier messages
• Later messages