0xbyt4 7baf370d3d chore(tui): capture signal-triggered gateway exits in crash log ... SIG_DFL for SIGPIPE means the kernel reaps the gateway subprocess the instant a background thread (TTS playback, silence callback, voice status emitter) writes to a stdout the TUI stopped reading — before the Python interpreter can run excepthook, threading.excepthook, atexit, or the entry.py post-loop _log_exit. Replace the three SIG_DFL / SIG_IGN bindings with a _log_signal handler that: - records which signal (SIGPIPE / SIGTERM / SIGHUP) fired and when; - dumps the main-thread stack at signal delivery AND every live thread's stack via sys._current_frames — the background-thread write that provoked SIGPIPE is almost always visible here; - writes everything to ~/.hermes/logs/tui_gateway_crash.log and prints a [gateway-signal] breadcrumb to stderr so the TUI Activity surfaces it as well. SIGINT stays ignored (TUI handles Ctrl+C for the user).		2026-04-23 16:18:15 -07:00
..
__init__.py	feat: new tui based on ink	2026-04-02 19:07:53 -05:00
entry.py	chore(tui): capture signal-triggered gateway exits in crash log	2026-04-23 16:18:15 -07:00
render.py	tui: inherit Python-side rendering via gateway bridge	2026-04-05 18:50:41 -05:00
server.py	chore(tui): dump gateway crash traces to ~/.hermes/logs/tui_gateway_crash.log	2026-04-23 16:18:15 -07:00
slash_worker.py	feat: personality	2026-04-08 00:15:15 -04:00