The GitHub Actions job "Tests (AMD)" on airflow.git/v3-2-test has succeeded. Run started by GitHub user pierrejeambrun (triggered by pierrejeambrun).
Head commit for run: 0fa7da1d2e4c35092a218738d9378ecfeeb6cb8e / github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> [v3-2-test] UI: Fix Graph layout for TaskGroup tasks wired to external nodes (#67720) (#67830) Open ``@task_group`` rendered with vertically-stacked internals and edges crossing the boundary whenever an internal task had a direct dependency on a node outside the group (an "escape edge" that bypassed the group's entry/exit interface). Dag execution was unaffected. Two underlying issues, both in the ELK graph-layout refactor from #65031: 1. ``hasUniformExternalConnectivity`` was too lenient — it fired whenever externally-connected children separately shared the same external sources OR the same external targets, instead of the canonical fan-in/fan-out pattern where every child has the same full ``(sources, targets)`` profile. On mixed-profile groups (entry + exits), it incorrectly fired and collapsed the author's deliberately- wired escape edges into a single group-level edge, hiding the intent. 2. When the optimisation did fire on an open group, ``rewriteGroupEdges`` was tuned for closed groups and dropped the group's internal edges too, leaving ELK with no internal-layout information for the children (the visible symptom in #67714). Fix: tighten ``hasUniformExternalConnectivity`` to require the full profile to match across externally-connected children, and add a ``preserveInternal`` option to ``rewriteGroupEdges`` so the canonical fan-in/fan-out path keeps internals intact. (cherry picked from commit 55780f2d3cd7db64bc6d1479b9da7bff765f046d) Closes: #67714 Co-authored-by: Rahul Vats <[email protected]> Report URL: https://github.com/apache/airflow/actions/runs/26756214170 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
