jason810496 opened a new pull request, #74040: URL: https://github.com/apache/airflow/pull/74040
STACKLINE related: #71929 Part of the native Dag e2e stack, split out of #74035. Builds on #74034 ([layer diff](https://github.com/apache/airflow/compare/jason/lang-sdk-e2e/02b-shared-dag-cycle-detection...jason/lang-sdk-e2e/03a-dag-processor-base)). ## Why A native Lang-SDK Dag file is parsed by a different child process than a Python Dag file (P4). Both need the same plumbing for the Dag processor manager. ## What changes No behavior change. `DagFileProcessorProcess` is split into a new `BaseDagFileProcessorProcess`, which holds what any parse child needs: the parse log, the requests answered with the API client, the parse result and the readiness check. `DagFileProcessorProcess` keeps the Python-specific start and callbacks. Each class declares its own `_request_handlers`, typed with itself, from the base's `_common_request_handlers`. ## How to test ```bash uv run --project airflow-core pytest airflow-core/tests/unit/dag_processing/test_processor.py airflow-core/tests/unit/dag_processing/test_manager.py -xvs ``` --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes, with help of Claude Code Opus 5.5 following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
