flyteorg/flyte

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

Open

#5.096 geöffnet am 22. März 2024

Auf GitHub ansehen
 (6 Kommentare) (2 Reaktionen) (0 zugewiesene Personen)Python (3.705 Stars) (378 Forks)batch import
enhancementgood first issueui

Beschreibung

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
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
half day
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
active
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
clear
Voraussetzungen
Basic understanding of Flyte cache serializationFamiliarity with Flyte UI codebase
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
70
Research-Richtung
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.