kacpermuda commented on issue #48928: URL: https://github.com/apache/airflow/issues/48928#issuecomment-2788746579
Checked again today with Celery, both with OL and without OL. In short, its always this error when changing state from UI while task is running (regardless whether we set success or failed state)(but for CeleryExecutor it's `SystemExit: -241` and not DB access error)  Used `breeze start-airflow -b postgres --executor CeleryExecutor` and `breeze start-airflow --integration openlineage -b postgres --executor=CeleryExecutor`. Here are the logs: [task_celery_mark_success_no_ol.txt](https://github.com/user-attachments/files/19662994/task_celery_mark_success_no_ol.txt) [task_celery_mark_failed_no_ol.txt](https://github.com/user-attachments/files/19662996/task_celery_mark_failed_no_ol.txt) [task_celery_mark_success_with_ol.txt](https://github.com/user-attachments/files/19662993/task_celery_mark_success_with_ol.txt) [task_celery_mark_failed_with_ol.txt](https://github.com/user-attachments/files/19662995/task_celery_mark_failed_with_ol.txt) [log_celery_worker_with_ol.txt](https://github.com/user-attachments/files/19662997/log_celery_worker_with_ol.txt) Verified again today on latest main on LocalExecutor as well (with and without OpenLineage) and it's still as described in the ticket: `RuntimeError: Direct database access via the ORM is not allowed in Airflow 3.0`. At least I couldn't reproduce the error from my message above (`[2025-04-08, 14:05:06] WARNING - Exception when importing 'airflow.providers.google.assets.gcs.sanitize_uri' from 'apache-airflow-providers-google' package: source="airflow.providers_manager" RuntimeError: Direct database access via the ORM is not allowed in Airflow 3.0`) that occurred when simply running the task, without any state modifications. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
