#732 local runs and tui should respect disable run cache Pull request opened by cosmicBboy This pull request introduces support for a run-level override to disable task result caching, ensuring that when caching is disabled for a run, no cache hits are reported, cache writes are skipped, and the UI reflects this status. The changes span the core execution logic, persistence layers, TUI display, and add comprehensive tests for the new behavior. Key changes include: Run cache disabling logic and propagation: • Added a

disable_run_cache

field to

TaskContext

, and ensured this flag is propagated through local and remote task execution, so that when it is set, cache reads and writes are skipped. Persistence and tracking: • Extended the database schema and record-keeping to include the

disable_run_cache

field, ensuring this information is stored and loaded with run records. (

src/flyte/_persistence/_db.py

,

src/flyte/_persistence/_recorder.py

,

src/flyte/_persistence/_run_store.py

,

src/flyte/cli/_tui/_tracker.py

) TUI (Terminal UI) display improvements: • Updated the TUI to display when run cache is disabled at the run level, both in cache icons and detail screens, overriding any cache hit/miss indicators. (

src/flyte/cli/_tui/_app.py

,

src/flyte/cli/_tui/_explore.py

) Testing: • Added and extended tests to verify that disabling run cache is correctly handled, persisted, and displayed in the TUI, including new test cases for the cache icon and run detail screen. (

tests/cli/test_tui_explore.py

,

tests/cli/test_tui_tracker.py

) These changes ensure that disabling task result caching for a run is respected throughout the system and clearly communicated to users. flyteorg/flyte-sdk