potiuk commented on issue #40097: URL: https://github.com/apache/airflow/issues/40097#issuecomment-2152653008
Hey @vincbeck @o-nikolas -> looks like we got it now when 2.9.2rc1 is using the old celery provider. Way to reproduce: 1. Run this: ``` breeze start-airflow --use-airflow-version 2.9.2rc1 --load-example-dags --load-default-connections --executor CeleryExecutor --airflow-extras celery ``` 2. Check installed packages: ``` root@c45830039533:/opt/airflow# pip freeze | grep celery apache-airflow-providers-celery==3.7.1 celery==5.4.0 root@c45830039533:/opt/airflow# pip freeze | grep apache-airflow apache-airflow==2.9.2rc1 apache-airflow-providers-celery==3.7.1 apache-airflow-providers-common-io==1.3.2 apache-airflow-providers-common-sql==1.14.0 apache-airflow-providers-fab==1.1.1 apache-airflow-providers-ftp==3.9.1 apache-airflow-providers-http==4.11.1 apache-airflow-providers-imap==3.6.1 apache-airflow-providers-smtp==1.7.1 apache-airflow-providers-sqlite==3.8.1 root@c45830039533:/opt/airflow# ``` 3) Connect to http://localhost:28080/ 4) Run "example_complex" dag 5) You will see `BaseExecutor.change_state() got an unexpected keyword argument 'remove_running' airflow_scheduler` - errors. I am afraid we will need to to handle back-compatibility there. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
