flyteorg/flyte

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

Open

#5096 opened on Mar 22, 2024

View on GitHub
 (6 comments) (2 reactions) (0 assignees)Python (3,705 stars) (378 forks)batch import
enhancementgood first issueui

Description

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

Contributor guide

Tech stack
typescriptreact
Domain
frontenddeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of Flyte cache serializationFamiliarity with Flyte UI codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
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.