flyteorg/flyte

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

Open

Aperta il 22 mar 2024

Vedi su GitHub
 (6 commenti) (2 reazioni) (0 assegnatari)Python (3705 star) (378 fork)batch import
enhancementgood first issueui

Descrizione

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

Guida contributor

Tech stack
typescriptreact
Dominio
frontenddeveloper experience
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
half day
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
active
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Basic understanding of Flyte cache serializationFamiliarity with Flyte UI codebase
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
70
Direzione di ricerca
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.