goldigd05 commented on issue #60059: URL: https://github.com/apache/airflow/issues/60059#issuecomment-3711180657
I have identified the root cause of this issue. When using GitDagBundle, runtime exceptions during DAG parsing (such as UnboundLocalError) are correctly caught and logged by the dag-processor, but fail to persist into the import_error table. This happens because the physical file path cannot be reliably mapped back to the bundle-relative path when the exception is raised inside the DAG factory, causing the ImportError DB insertion to be silently skipped. Expected behavior: Runtime DAG parsing errors in GitDagBundle should be persisted and visible in the Import Errors UI, consistent with LocalDagBundle and SyntaxError handling. I am working on a fix that: - Resolves bundle metadata before DAG execution - Adds a safe fallback for bundle path mapping - Ensures import errors are always persisted for GitDagBundle I am happy to submit a PR with tests. -- 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]
