[BUG] Fix ArrayNode not reporting terminal state in TaskExecutionEvent

[pvditt]

Describe the bug

ArrayNode currently reports events identically to maptask plugin where we encapsulate subNode executions within the ExternalResourceInfo field in TaskExecutionEvent proto message. The ExternalResourceInfo proto message has a phase field, which corresponds to the phase of the subNode. The top-level node phase is reported using (and displayed in the UI from) the NodeExecutionEvent. So there is a task phase on the TaskExecutionEvent that is not currently being used.

However, this phase is incorrect. We attempt to set it on terminal states here , but this code is never reached because terminal states return prematurely. We need to ensure that the phase on the TaskExecutionEvent is correctly set on terminal phases.

Expected behavior

task execution phases match terminal state for array nodes

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[cw75]

@RunLLM is there a pull request that fixes this issue?

[runllm]

To address the issue of ArrayNode not reporting the terminal state in TaskExecutionEvent, a pull request titled "[Bug] correctly set task execution phase for terminal array node" (PR #5136) is currently open. This PR aims to ensure the correct phase is set in task execution events for terminal ArrayNodes. It is still under review and not yet merged.

Would you like more details on the changes proposed in this pull request?

Sources:

• Discuss Flyte
• Discuss Flyte
• GitHub PR #5136

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[pvditt]

fixes:
#5680
#5681
#5451
oops - this is the incorrect issue for these

[pvditt]

@cw75 we just upstreamed a few of the fixes. Will close this after #5681 is merged