jason810496 opened a new pull request, #73442: URL: https://github.com/apache/airflow/pull/73442
# TS SDK: answer the Dag-parsing request from bundle.serve - **Depends on the PR for `feature/ts-sdk/serialize-native-dag` getting merged first** (only the last commit is new here). - **Diff for early review**: https://github.com/jason810496/airflow/compare/feature/ts-sdk/serialize-native-dag...feature/ts-sdk/answer-dag-parse-request - **next**: `feature/ts-sdk/conditional-branching` ## Why The parse path existed but answered with an empty result, so a natively declared Dag never reached the Dag processor. ## How - `bundle.serve()` answers a parse request with the Dags the bundle declared in TypeScript. A Dag known only through task handlers is left out: its graph belongs to the Python file that declares it. - No handler body runs. A task reference is inert, so reading a Dag only walks what its module already built. - A Dag that cannot be read or serialized becomes an import error against the file, the way a Python Dag file that raises does, so one broken Dag does not take out the others a bundle serves. ## What - `handleParse` serializes each native Dag and collects per-Dag failures into `import_errors`. - Reading a bundle's Dags is what closes them, so an uncalled task or a cycle surfaces here rather than crashing the runtime. Needs the core-side coordinator parse hooks and wire messages before anything sends the request this answers. --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes, with help of Claude Code Opus 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]
