[BUG] Too many map executions shown in Flyte console

[fg91]

Describe the bug

If one creates a map task over e.g. 5 inputs and on the platform side configures e.g. 2 log links for map tasks, FlyteConsole shows 10 map executions instead of 5.

Expected behavior

The number of executions shown in FlyteConsole should be equal to the number of pods.

Additional context to reproduce

Example from the docs:

import functools
from flytekit import map_task, task, workflow


@task
def multi_input_task(quantity: int, price: float, shipping: float) -> float:
    return quantity * price * shipping


@workflow
def multiple_workflow(list_q: list[int] = [1, 2, 3, 4, 5], p: float = 6.0, s: float = 7.0) -> list[float]:
    partial_task = functools.partial(multi_input_task, price=p, shipping=s)
    return map_task(partial_task)(quantity=list_q)

Screenshots

For two log links configured, FlyteConsole shows 10 executions instead of 5:

If we configure a third log link, the number of shown executions is 15.

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

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[dosubot[bot]]

🤖

Hello @fg91,

I'm Dosu, a bot here to assist you with bugs, answer your questions, and guide you on your journey to becoming a contributor. While we wait for a human maintainer, I'm here to help you out! It's nice to meet you and I look forward to helping you with your issue.

Thank you for reporting this issue. It seems similar to a previously resolved issue: [BUG] Mapped tasks with more than on log links do not render correctly. The solution to that issue was implemented in these pull requests: PR 725 and PR 727. However, I couldn't find the exact changes made in these pull requests within the repository.

Regarding the function of log links in FlyteConsole, they provide direct access to the logs of the tasks executed as part of the workflows. In the context of map tasks, each task execution in the map task will have its own set of logs. The log links in the FlyteConsole will direct you to the logs of each individual task execution. This behavior might depend on the specific configuration of your Flyte deployment and the plugins you are using. You can find more details in the task_logs.yaml file.

Given the information available, it's difficult to provide a definitive solution to your issue. Could you please provide more details about your Flyte deployment and configuration, especially the plugins you are using? This will help in understanding the issue better and finding a suitable solution.

Sources

• [BUG] Mapped tasks with more than on log links do not render correctly
• kustomize/overlays/eks/flyte/config/propeller/plugins/task_logs.yaml

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[eapolinario]

@fg91 , do you also see the same with array node map tasks?

[fg91]

@fg91 , do you also see the same with array node map tasks?

Yes, we do 👍

[fg91]

The Flyteconsole/UI revamp released with 1.12 appears to have fixed this.