The GitHub Actions job "Tests (ARM)" on airflow.git/main has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 2de022380ce4fc626d382582fffb1fa62ca8e18a / Jarek Potiuk <[email protected]> Add Task SDK, Go and Java SDK execution architecture diagrams (#69750) * Add Task SDK, Go and Java SDK execution architecture diagrams Add graphviz-generated diagrams to the architecture overview showing how a task actually runs across the different SDKs, and embed them in core-concepts/overview.rst: - Python Task SDK: supervised (two native OS processes over a msgpack socket) vs native/in-process paths, plus a numbered message-flow sequence. - Go SDK: standalone edge worker pulling from the Edge API, task talks to the Execution API directly. - Java (JVM) SDK: Coordinator layer reusing the Python Supervisor, driving a JVM subprocess over loopback TCP, with an architecture diagram and a numbered execution-workflow sequence. * Draw Task and Java SDK execution flows as true sequence diagrams The message-flow diagrams added earlier in this PR drew every step on a single vertical spine, so the request/response round-trips between the task runtime and the Supervisor were hard to follow. Responding to review feedback, redraw them as true sequence diagrams — one lifeline per participant with the Supervisor in the middle — so each round-trip reads as arrows going back and forth between neighboring lifelines, with straight message arrows and margined labels. Report URL: https://github.com/apache/airflow/actions/runs/29701457273 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
