bugraoz93 commented on issue #49330: URL: https://github.com/apache/airflow/issues/49330#issuecomment-2810483602
> @bugraoz93 Thats only if you have a dag-processor running. in airflow 2.10.5 this command reads directly from the repo rather than the db. The current implementation breaks local DagBag development and requires you to have a dag-processor job actively running during dag development. We should support both scenarios > > I have a setup where I just have the following settings in a source_me in my dags repository and I use `airflow dags list-import-errors` > while editing my dags > > ``` > AIRFLOW_HOME = '<dags_repo>/run' > AIRFLOW__CORE__DAGS_FOLDER = <dags_repo> > AIRFLOW__CORE__LOAD_EXAMPLES = false > ``` > in this setup `airflow info` will auto create a `airflow.cfg` and `airflow.db` in the `dags_repo/run` area. Its a downgrade if we need to `airflow dags reserialize` and then `airflow dags list-import-errors` every time instead of just `airflow dags list-import-errors` to figure out whats wrong ( which was the case in airflow 2 ) I want to clarify some parts. I see that the issue opened as 3.0.0, which is the current main branch. In Airflow 3.0 (main branch), there will be Dag Processors running. All the CLI commands are updated according to the dag bundle and versioning, which is managed by Dag Processors. So, in the context of 3.0.0, I think this is not a problem but already planned changes. See https://github.com/apache/airflow/blob/main/airflow-core/newsfragments/45729.significant.rst Current latest development version of 2.10 https://github.com/apache/airflow/tree/v2-10-test Stable https://github.com/apache/airflow/tree/v2-10-stable -- 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]
