dev  

Messages by Thread

• [DISCUSS] Handling cyclic TaskGroup dependencies (Grid/Graph 500 since 3.3.1) Dheeraj Turaga
• [VOTE] Airflow Providers, release preparation date 2026-09-22 Shahar Epstein
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-22 Aaron Chen
  • RE: [VOTE] Airflow Providers, release preparation date 2026-09-22 Subhramit B.B.
• CONFLUENCE 2026 x Apache Airflow — Open-Source & Linux Bootcamp Collaboration ieee.vips.edu via dev
• [DISCUSS] Human Summary section in agent-drafted PR descriptions Jarek Potiuk
  • Re: [DISCUSS] Human Summary section in agent-drafted PR descriptions Shahar Epstein
  • Re: [DISCUSS] Human Summary section in agent-drafted PR descriptions Ash Berlin-Taylor
  • Re: [DISCUSS] Human Summary section in agent-drafted PR descriptions Jarek Potiuk
• [LAZY CONSENSUS] Human Summary section in agent-drafted PR descriptions Jarek Potiuk
  • Re: [LAZY CONSENSUS] Human Summary section in agent-drafted PR descriptions Ash Berlin-Taylor
  • Re: [LAZY CONSENSUS] Human Summary section in agent-drafted PR descriptions Jarek Potiuk
  • Re: [LAZY CONSENSUS] Human Summary section in agent-drafted PR descriptions Jarek Potiuk
  • Re: [LAZY CONSENSUS] Human Summary section in agent-drafted PR descriptions Jarek Potiuk
• [VOTE] Naming of the `.batch(size=)` method in AIP-104 (Iterable Tasks) Blain David
  • Re: [VOTE] Naming of the `.batch(size=)` method in AIP-104 (Iterable Tasks) Shahar Epstein
  • Re: [VOTE] Naming of the `.batch(size=)` method in AIP-104 (Iterable Tasks) Ash Berlin-Taylor
  • Re: [VOTE] Naming of the `.batch(size=)` method in AIP-104 (Iterable Tasks) Ash Berlin-Taylor
  • Re: [VOTE] Naming of the `.batch(size=)` method in AIP-104 (Iterable Tasks) Ash Berlin-Taylor
  • Re: [VOTE] Naming of the `.batch(size=)` method in AIP-104 (Iterable Tasks) David Blain
  • Re: [VOTE] Naming of the `.batch(size=)` method in AIP-104 (Iterable Tasks) Jarek Potiuk
• [DISCUSS] Proposal for "Time-Travel Pipeline Runs" Daniyar Nurtailakov
  • Re: [DISCUSS] Proposal for "Time-Travel Pipeline Runs" Ash Berlin-Taylor
• [DISCUSS] Proposal for "Self-Healing Retries" Daniyar Nurtailakov
• Airflow Open Spaces at PyCon TW 2026 dev.wei-lee.me via dev
  • Re: Airflow Open Spaces at PyCon TW 2026 Yeonguk Choo
  • Re: Airflow Open Spaces at PyCon TW 2026 Jarek Potiuk
• [REMINDER]: Airflow Dev call on 24th September Vikram Koka via dev
  • Re: [REMINDER]: Airflow Dev call on 24th September Jarek Potiuk
• [DISCUSS] Dynamic discovery of DAG bundle configurations without restart Sameer Raj via dev
• [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Vincent Beck
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Sameer Mesiah
  • RE: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Damian Shaw
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jake McGrath via dev
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Henry Chen
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Vincent Beck
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Henry Chen
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Przemysław Mirowski
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Sumit Maheshwari
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Ankit Chaurasia
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Sameer Mesiah
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jyun-An Chen
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Sameer Mesiah
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Aaron Chen
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Sameer Mesiah
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Andrew Chang
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Christos Bisias
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Yuseok Jo
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Andrew Chang
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Ash Berlin-Taylor
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Zach Gottesman via dev
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Sean Muth
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Pratiksha Badheka
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
  • Re: [LAZY CONSENSUS] Limiting number of opened pull requests for users without write access Jarek Potiuk
• [ANNOUNCE] Apache Airflow Python Client 3.3.2 Released Rahul Vats
  • Re: [ANNOUNCE] Apache Airflow Python Client 3.3.2 Released Amogh Desai
• [RESULT][VOTE] Release Airflow Python Client 3.3.2 from 3.3.2rc2 Rahul Vats
• [DISCUSS] New Community Provider: Modal Kaxil Naik
  • Re: [DISCUSS] New Community Provider: Modal Amogh Desai
  • Re: [DISCUSS] New Community Provider: Modal Jarek Potiuk
  • Re: [DISCUSS] New Community Provider: Modal Kaxil Naik
  • Re: [DISCUSS] New Community Provider: Modal Amogh Desai
  • Re: [DISCUSS] New Community Provider: Modal Vikram Koka via dev
• [DISCUSS] Separate dag bundle discovery and import roots Sameer Raj
  • Re: [DISCUSS] Separate dag bundle discovery and import roots Jarek Potiuk
  • Re: [DISCUSS] Separate dag bundle discovery and import roots Amogh Desai
  • Re: [DISCUSS] Separate dag bundle discovery and import roots Sameer Raj
  • Re: [DISCUSS] Separate dag bundle discovery and import roots Jarek Potiuk
  • Re: [DISCUSS] Separate dag bundle discovery and import roots Sameer Raj
  • Re: [DISCUSS] Separate dag bundle discovery and import roots Jarek Potiuk
• [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Ash Berlin-Taylor
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jyun-An Chen
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Ferruzzi, Dennis
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Ash Berlin-Taylor
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Ash Berlin-Taylor
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Christos Bisias
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Ash Berlin-Taylor
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Justin Pakzad
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Christos Bisias
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Ash Berlin-Taylor
  • Re: [DISCUSS] Run CI for external contributions in contributor forks Jarek Potiuk
• [DISCUSS] Anomaly monitoring and guardrails for the Airflow AWS account: AIP-119 Jarek Potiuk
  • Re: [DISCUSS] Anomaly monitoring and guardrails for the Airflow AWS account: AIP-119 Shahar Epstein
• [VOTE] Release Apache Airflow Python Client 3.3.2 from 3.3.2rc1 Rahul Vats
  • Re: [VOTE] Release Apache Airflow Python Client 3.3.2 from 3.3.2rc1 Jarek Potiuk
  • Re: [VOTE] Release Apache Airflow Python Client 3.3.2 from 3.3.2rc1 Jarek Potiuk
  • Re: [VOTE] Release Apache Airflow Python Client 3.3.2 from 3.3.2rc1 Kaxil Naik
  • Re: [VOTE] Release Apache Airflow Python Client 3.3.2 from 3.3.2rc1 Amogh Desai
  • Re: [VOTE] Release Apache Airflow Python Client 3.3.2 from 3.3.2rc1 Wei Lee
• [DISCUSS] AIP-118: Self-hosted runners for Apache Airflow CI Shahar Epstein
  • Re: [DISCUSS] AIP-118: Self-hosted runners for Apache Airflow CI Jarek Potiuk
  • Re: [DISCUSS] AIP-118: Self-hosted runners for Apache Airflow CI Jarek Potiuk
  • RE: [DISCUSS] AIP-118: Self-hosted runners for Apache Airflow CI Subhramit B.B.
• [ANNOUNCE] Apache Airflow 3.3.2 Released Rahul Vats
• [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Blain David
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Ash Berlin-Taylor
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Constance Martineau via dev
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Jarek Potiuk
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Ash Berlin-Taylor
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Shahar Epstein
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Blain David
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Blain David
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Jarek Potiuk
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Amogh Desai
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Ash Berlin-Taylor
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) constance.astronomer.io via dev
  • Re: [DISCUSS] Naming of `.batch(size=)` in AIP-104 (Iterable Tasks and Dynamic Task Batching) Jarek Potiuk
• [RESULT][VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Rahul Vats
  • Re: [RESULT][VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Jarek Potiuk
  • Re: [RESULT][VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Shahar Epstein
• ANNOUNCEMENT: Airflow Summit Online Reconnect 2026 registration and CFP open Mara Ruvalcaba
• Apache Airflow Birthday Party in Seoul on Oct 7 🎂 Yeonguk Choo
  • Re: Apache Airflow Birthday Party in Seoul on Oct 7 🎂 Jarek Potiuk
  • Re: Apache Airflow Birthday Party in Seoul on Oct 7 🎂 Yuseok Jo
• [Meeting Notes] Airflow dev call - 10 September 2026 Vikram Koka via dev
• [ANNOUNCE] Apache Airflow Providers prepared on 2026-09-09 are released Beck, Vincent
• [RESULT][VOTE] Airflow Providers - release preparation date 2026-09-09 Vincent Beck
• [VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Rahul Vats
  • Re: [VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Jarek Potiuk
  • Re: [VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Amogh Desai
  • Re: [VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Kaxil Naik
  • Re: [VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Atul Kumar Singh via dev
  • Re: [VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Wei Lee
  • Re: [VOTE] Release Airflow 3.3.2 from 3.3.2rc1 & Task SDK 1.3.2 from 1.3.2rc1 Blain David
• [DISCUSS] Multiple pool requirements per task Ramachandra Nalam
  • Re: [DISCUSS] Multiple pool requirements per task Ramachandra Nalam
• [DISCUSS] Newsfragments: when to add one Kaxil Naik
  • Re: [DISCUSS] Newsfragments: when to add one Elad Kalif
  • Re: [DISCUSS] Newsfragments: when to add one Pierre Jeambrun
  • Re: [DISCUSS] Newsfragments: when to add one Vikram Koka via dev
  • Re: [DISCUSS] Newsfragments: when to add one Ferruzzi, Dennis
  • Re: [DISCUSS] Newsfragments: when to add one Jarek Potiuk
• Airflow Providers, release preparation date 2026-09-09 Bingqin Wang
• [DISCUSS] Asset events batched into a single DagRun, make it configurable and reconsider default Constance Martineau via dev
  • Re: [DISCUSS] Asset events batched into a single DagRun, make it configurable and reconsider default Jake McGrath via dev
  • Re: [DISCUSS] Asset events batched into a single DagRun, make it configurable and reconsider default Jarek Potiuk
  • Re: [DISCUSS] Asset events batched into a single DagRun, make it configurable and reconsider default Jarek Potiuk
  • Re: [DISCUSS] Asset events batched into a single DagRun, make it configurable and reconsider default Philippe Gagnon via dev
  • Re: [DISCUSS] Asset events batched into a single DagRun, make it configurable and reconsider default Kaxil Naik
  • Re: [DISCUSS] Asset events batched into a single DagRun, make it configurable and reconsider default Constance Martineau via dev
• [VOTE] Airflow Providers, release preparation date 2026-09-09 Vincent Beck
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-09 Niko Oliveira
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-09 Sameer Mesiah
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-09 Wei Lee
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-09 Amogh Desai
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-09 Aaron Chen
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-09 Jarek Potiuk
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-09 Shahar Epstein
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-09 Jarek Potiuk
  • Re: [VOTE] Airflow Providers, release preparation date 2026-09-09 Bingqin Wang
• [DISCUSS] "scheduled" triaging and security issues - with Airflow as engine Jarek Potiuk
  • Re: [DISCUSS] "scheduled" triaging and security issues - with Airflow as engine Jarek Potiuk
• September 2026 Airflow Monthly Town Hall Recording Mico Yuk via dev
• [DISCUSS] Microsoft Fabric Provider Blain David
  • Re: [DISCUSS] Microsoft Fabric Provider Jarek Potiuk
  • Re: [DISCUSS] Microsoft Fabric Provider Aaron Chen
  • Re: [DISCUSS] Microsoft Fabric Provider Niko Oliveira
  • Re: [DISCUSS] Microsoft Fabric Provider Vikram Koka via dev
• [DISCUSS] Opt-in re-firing of asset partitions on late/corrected data Z II
  • Re: [DISCUSS] Opt-in re-firing of asset partitions on late/corrected data Ramzi Alashabi
• [DISCUSS] New Community Provider: DuckDB Niko Oliveira
  • Re: [DISCUSS] New Community Provider: DuckDB Blain David
  • Re: [DISCUSS] New Community Provider: DuckDB Dev-iL
  • Re: [DISCUSS] New Community Provider: DuckDB Jarek Potiuk
  • Re: [DISCUSS] New Community Provider: DuckDB Niko Oliveira
  • Re: [DISCUSS] New Community Provider: DuckDB Julian LaNeve via dev
  • Re: [DISCUSS] New Community Provider: DuckDB Niko Oliveira
  • Re: [DISCUSS] New Community Provider: DuckDB Amogh Desai
  • Re: [DISCUSS] New Community Provider: DuckDB Sameer Mesiah
  • Re: [DISCUSS] New Community Provider: DuckDB Shubham Raj
  • Re: [DISCUSS] New Community Provider: DuckDB Kaxil Naik
  • Re: [DISCUSS] New Community Provider: DuckDB Vikram Koka via dev
  • Re: [DISCUSS] New Community Provider: DuckDB Wei Lee
  • Re: [DISCUSS] New Community Provider: DuckDB Aaron Chen
  • Re: [DISCUSS] New Community Provider: DuckDB Niko Oliveira
• [REMINDER]: Airflow Dev call on 10th September Vikram Koka via dev

• Earlier messages