<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ida-tui.git/idatui/client.py, branch main</title>
<subtitle>tui for headless ida</subtitle>
<id>https://git.sl0p.foo/ida-tui.git/atom/idatui/client.py?h=main</id>
<link rel='self' href='https://git.sl0p.foo/ida-tui.git/atom/idatui/client.py?h=main'/>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/ida-tui.git/'/>
<updated>2026-07-09T09:55:43Z</updated>
<entry>
<title>keep idle workers alive: bump_idle_ttl + KeepAlive heartbeat</title>
<updated>2026-07-09T09:55:43Z</updated>
<author>
<name>blasty</name>
<email>blasty@local</email>
</author>
<published>2026-07-09T09:55:43Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/ida-tui.git/commit/?id=21d2cbbfcdbb712b907573b784bc9d98d5c5e648'/>
<id>urn:sha1:21d2cbbfcdbb712b907573b784bc9d98d5c5e648</id>
<content type='text'>
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 -&gt; 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.
</content>
</entry>
<entry>
<title>harden client: transparent session auto-recovery + stress suite</title>
<updated>2026-07-09T09:22:18Z</updated>
<author>
<name>blasty</name>
<email>blasty@local</email>
</author>
<published>2026-07-09T09:22:18Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/ida-tui.git/commit/?id=90636755b26c5dbee8acdda5e37c7aff9e896854'/>
<id>urn:sha1:90636755b26c5dbee8acdda5e37c7aff9e896854</id>
<content type='text'>
- auto-recover stale db ("Session not found" after server restart): drop pin,
  re-resolve sole session, retry once. Only when db was auto-injected; never
  silently switches an explicitly-pinned db (auto_recover_session gate).
- tests/serverctl.sh: start/stop/kill9/ready control over spawn.sh
- tests/stress_client.py: 6 adversarial scenarios, 24 assertions:
  dead-port fail-fast, tight-timeout recovery, worker crash, full restart
  (naive auto-recovery + no-autoswitch), 300/16 concurrency, kill-under-churn.
  All clean: no hangs, no deadlocks, no non-IDAError leaks.
</content>
</entry>
<entry>
<title>persistent MCP client: warm handshake, keep-alive pool, error taxonomy, thread-safe</title>
<updated>2026-07-09T09:14:23Z</updated>
<author>
<name>blasty</name>
<email>blasty@local</email>
</author>
<published>2026-07-09T09:14:23Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/ida-tui.git/commit/?id=eec630887ce72a7dafae4c33f5e85ad7c746b038'/>
<id>urn:sha1:eec630887ce72a7dafae4c33f5e85ad7c746b038</id>
<content type='text'>
- IDAClient: single handshake, ~7ms warm calls (vs ~60ms cold CLI)
- keep-alive connection pool over http.client; concurrent-safe (40 threads OK)
- grounded error taxonomy: IDAToolError on isError, soft per-item errors as data
- session-expiry recovery (404 -&gt; re-handshake -&gt; retry), bounded transport retries
- auto db-injection + resolve_db (ignores stale empty-id sessions)
- live smoke test: 13/13 pass
</content>
</entry>
</feed>
