Shlomit-B commented on issue #53971: URL: https://github.com/apache/airflow/issues/53971#issuecomment-3172005413
> [@Shlomit-B](https://github.com/Shlomit-B) Sure, lets talk about an implementation plan. What is your idea here? At the moment I see two main options: 1. As you suggested, using a special module-level variable (__airflow_dag_parsing_errors). It’s simple to adopt with minimal changes. 2. Providing an explicit safe wrapper (e.g `@safe_dag_factory` decorator, context manager, function, or a combination—we can discuss what fits best). This wrapper would catch exceptions per DAG, safely register valid DAGs, and consistently collect error info. I tend to prefer option 2, as it seems more consistent and robust. What are your thoughts? -- 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]
