github-actions[bot] opened a new pull request, #67830:
URL: https://github.com/apache/airflow/pull/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)
   
   Co-authored-by: Rahul Vats <[email protected]>
   Closes: #67714


-- 
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]

Reply via email to