diff options
| author | blasty <blasty@local> | 2026-07-09 11:55:43 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-09 11:55:43 +0200 |
| commit | 21d2cbbfcdbb712b907573b784bc9d98d5c5e648 (patch) | |
| tree | 8d2c94975c30e13501f0c8c8785230cae235ae98 /pyproject.toml | |
| parent | domain/paging layer: FunctionIndex, block-cached DisasmModel, decompile, resolve (diff) | |
| download | ida-tui-21d2cbbfcdbb712b907573b784bc9d98d5c5e648.tar.gz ida-tui-21d2cbbfcdbb712b907573b784bc9d98d5c5e648.tar.xz ida-tui-21d2cbbfcdbb712b907573b784bc9d98d5c5e648.zip | |
keep idle workers alive: bump_idle_ttl + KeepAlive heartbeat
Root cause: idalib workers run an idle watchdog (worker_lifecycle.py) that
self-exits after idle_ttl_sec (default 600s) of no requests -- deliberate
resource hygiene for a shared/ephemeral supervisor, wrong for an interactive
TUI. CLI-opened startup binary always gets 600s (no flag).
Fix (both verified against a 12s-TTL session):
- IDAClient.bump_idle_ttl(1e9): re-open (idempotent) re-applies TTL, no upper
cap -> effectively immortal. Primary fix, call once at startup.
- IDAClient.keepalive()/KeepAlive: background server_health heartbeat resets the
watchdog; covers adopted sessions too. Safety net.
tests/test_keepalive.py: 4/4 (heartbeat + bump both keep a short-TTL worker
alive past 2x TTL). docs updated with why + fix.
Diffstat (limited to 'pyproject.toml')
0 files changed, 0 insertions, 0 deletions