Also a small comment from resolving a failed CI: we need to ensure we merge the outstanding RCs of providers before releasing the final version of 3.4.0 (or other final versions) - because for example rc1 of 3.4.0 is tested with 1.1.0rc1 of common-ai - so we need to make sure either to release the final providers before or yank rcs when we gave up on releasing the provider's rcs (otherwise release of 3.4.0 will fail). Fix in https://github.com/apache/airflow/pull/75919
J. On Thu, Oct 29, 2026 at 12:54 AM Andrew Chang <[email protected]> wrote: > -1 (non-binding) > > I found a scheduler bug that seems related to #70972. > > Long story short, when users use asset events to schedule their tasks and > the events accumulate to a specific amount (about 7000~9000), the scheduler > could crash, and users wouldn't be able to restart their scheduler again. > > I've reported it in the 3.4.0rc1 test tracking issue: > https://github.com/apache/airflow/issues/75865#issuecomment-6483614606 > > TBH, reaching this condition, 7000 to 9000 accumulated asset events, is not > very common. > But the consequence is quite serious -- I think it is worth another look > before we release. > > Thanks, > Andrew >
