moomindani commented on issue #51598: URL: https://github.com/apache/airflow/issues/51598#issuecomment-4765005641
I confirmed this bug — it reproduces on `main` (Airflow 3) as well. The root cause is in `DatabricksWorkflowTaskGroup.__exit__()`: when `>>` is called before the `with` block, the `launch` task doesn't exist yet, so the dependency is recorded on the task group but never transferred to `launch`. Both `upstream` and `downstream` directions are affected. @shubhgurav0590 — your proposed fix in [#67369](https://github.com/apache/airflow/pull/67369#issuecomment-2905764696) (transferring `self.upstream_task_ids` to the launch task in `__exit__`) looks the right approach. You'll also want to handle `self.downstream_task_ids` to leaf tasks for the symmetric case. Feel free to reopen or open a fresh PR if you're still interested. --- Drafted-by: Claude Code (Opus 4.8); reviewed by @moomindani before posting -- 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]
