#729 add support for local retries, support tui Pull request opened by cosmicBboy This pull request introduces robust support for task retries in local runs, including exponential backoff and detailed tracking of individual retry attempts. The changes span the controller logic, persistence layer, and the TUI, allowing users to view and navigate all attempts for each action. The most important changes are grouped below. Retry logic and backoff improvements • Added local retry backoff defaults (

_MIN_BACKOFF_ON_ERR_SEC

,

_BACKOFF_MULTIPLIER

) and implemented exponential backoff for task retries in

_local_controller.py

. Retries are now tracked and attempts are recorded, including failures and completions. [1] [2] [3] Persistence and tracking of attempts • Extended the database schema to record

attempt_count

and

attempts_json

, and added new methods in

_run_store.py

for recording start, completion, and failure of individual attempts. Each attempt is stored with its status, outputs, error, and timestamps. [1] [2] [3] [4] [5] [6] • Enhanced run listing to include aggregate retry stats (

max_attempts_used

,

retried_actions

) and updated row parsing to handle new attempt fields. [1] [2] TUI enhancements for retry visibility • Updated the TUI label logic to display the number of attempts for each action and added controls for navigating between attempts in the detail panel. [1] [2] [3] • Implemented selection and navigation of previous/next attempts, and improved detail rendering to show attempt-specific information, including the current and total attempts. [1] [2] [3] [4] flyteorg/flyte-sdk