teknium1 365813a72b fix: resolve rebase conflict in _teardown_session worker cleanup ... Main folded slash_worker.close() into _finalize_session (the single _finalized-guarded chokepoint) while #42143 was open. The rebase conflicted with the PR's worker-close in _teardown_session. Keep both — they target the same #38095 leak and _SlashWorker.close() is idempotent (_closed/poll()-guarded) — so callers reaching _teardown_session without the real _finalize_session (and the PR's own tests, which monkeypatch _finalize_session out) still reap the worker. Same for _shutdown_sessions, now routed through the unified _close_session_by_id funnel.		2026-06-08 10:02:05 -07:00
..
__init__.py	feat: new tui based on ink	2026-04-02 19:07:53 -05:00
entry.py	perf(tui): stop slow/dead MCP servers from freezing TUI startup	2026-05-30 02:53:37 -07:00
event_publisher.py	chore: address copilot comments	2026-04-24 12:51:04 -04:00
render.py	tui: inherit Python-side rendering via gateway bridge	2026-04-05 18:50:41 -05:00
server.py	fix: resolve rebase conflict in _teardown_session worker cleanup	2026-06-08 10:02:05 -07:00
slash_worker.py	fix(tui-gateway): reap leaked slash_worker sessions on disconnect + active_list liveness (re-scoped onto current main)	2026-06-08 10:02:05 -07:00
transport.py	fix(tui-gateway): harden stdio transport against half-closed pipes + SIGTERM races (#17118)	2026-04-28 17:54:06 -05:00
ws.py	fix(tui-gateway): reap leaked slash_worker sessions on disconnect + active_list liveness (re-scoped onto current main)	2026-06-08 10:02:05 -07:00