flyteorg/flyte

[UI Feature] The UI should show that a task is pending due to `cache_serialize=True`

Open

#5,096 创建于 2024年3月22日

在 GitHub 查看
 (6 评论) (2 反应) (0 负责人)Python (3,705 star) (378 fork)batch import
enhancementgood first issueui

描述

Motivation: Why do you think this is important?

Cache serializing is a convenient mechanism to prevent expensive computation to be performed multiple times in parallel.

However, when a task is pending because of cache_serialize=True, there is no way for users to see that this is the reason and not a potential other problem.

Goal: What should the final outcome look like, ideally?

When a task is pending because it is waiting for another execution with the same cache version and input kwargs, the UI should mention this and provide a link to the execution blocking the one at hand.

Propose: Link/Inline OR Additional context

No response

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

  • Yes

Have you read the Code of Conduct?

  • Yes

贡献者指南

技术栈
typescriptreact
领域
frontenddeveloper experience
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic understanding of Flyte cache serializationFamiliarity with Flyte UI codebase
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
70
研究方向
Investigate the Flyte UI repository (flyteorg/flyteconsole) to find the component that displays task execution status. Look for how the 'pending' state is currently communicated. The backend likely exposes cache serialization status via the FlyteAdmin API; check the cache serialize field in execution data. Implement a UI element that shows a message like 'Waiting for another execution with same cache key' with a link to the blocking execution. The link should point to the execution details page. Consider reusing existing 'ExecutionLink' or similar component.