$jM2ddlZddlZejddZer$eejvrejdedejDe_ddlZddlZddl Z ddl Z ddl Z ddl m Z ddlmZmZmZmZddlmZejeZdadd Zd Zdefd Zd eddfd Zee dre j e j e j!ee dre j e j"eee dre j e j#en"ee dre j e j$eee dre j e j%e j!de&ddfdZ'ddeddfdZ(dZ)edkr e)dSdS)NHERMES_PYTHON_SRC_ROOTcg|]}|dv| S)>r.).0ps 0/usr/local/lib/hermes-agent/tui_gateway/entry.py r s" 6 6 6!1I#5#5A#5#5#5)server) _CRASH_LOGdispatch resolve_skin write_json) TeeTransportreturnctjd}|sdSddlm}t t j||t _dS)aMirror every dispatcher emit to the dashboard sidebar via WS. Activated by `HERMES_TUI_SIDECAR_URL`, set by the dashboard's ``/api/pty`` endpoint when a chat tab passes a ``channel`` query param. Best-effort: connect failure or runtime drop falls back to stdio-only. HERMES_TUI_SIDECAR_URLNr)WsPublisherTransport)osenvirongettui_gateway.event_publisherrrr _stdio_transport)urlrs r _install_sidecar_publisherr sc *..1 2 2C @@@@@@*!5!5c!:!:Fr g?ctjdpd}|stS t |}n#t $r tcYSwxYw|dkr|ntS)N#HERMES_TUI_GATEWAY_SHUTDOWN_GRACE_Srr)rrrstrip_DEFAULT_SHUTDOWN_GRACE_Sfloat ValueError)rawvalues r _shutdown_grace_secondsr&>s :>>? @ @ FB M M O OC )(()c  )))(((()AII55#<$rwxYw)uCapture WHICH thread and WHERE a termination signal hit us. SIG_DFL for SIGPIPE kills the process silently the instant any background thread (TTS playback, beep, voice status emitter, etc.) writes to a stdout the TUI has stopped reading. Without this handler the gateway-exited banner in the TUI has no trace — the crash log never sees a Python exception because the kernel reaps the process before the interpreter runs anything. Termination semantics: ``sys.exit(0)`` here used to race the worker pool — a thread holding ``_stdout_lock`` mid-flush would block the interpreter shutdown indefinitely. We now log the stack, give the process the configured shutdown grace (``HERMES_TUI_GATEWAY_SHUTDOWN_GRACE_S``, default ``_DEFAULT_SHUTDOWN_GRACE_S``) to drain naturally on a background thread, and fall back to ``os._exit(0)`` so a wedged write/flush can never strand the process. )SIGPIPESIGTERMSIGHUPSIGINTSIGBREAKNzsignal Texist_okautf-8encodingz === u received · %Y-%m-%d %H:%M:%S === z&main-thread stack at signal delivery: )filerz --- thread z (id=z) --- rz[gateway-signal] r6flushrc.tjddS)Nr)r_exitrr r _hard_exitz_log_signal.._hard_exitys  r rN) getattrsignalintrrmakedirspathdirnameropenwritetimestrftime traceback print_stack threading_activeitemsnamejoin format_stacksys_current_frames ExceptionprintstderrTimerr&daemonstartexit SystemExit) r'frame _signal_names_attr_sigrLf _threadingtidthr;timers r _log_signalrbIs*%'MG--vud++  ',M#d)) $   V%7v%7%7 8 8D  BGOOJ//$???? *cG 4 4 4 Y GGVVVDM:M,N,NVVV    ABBB%e!4444 + * * *%-3355 Y YRBBBcBBBCCC 6s7J7L7L7P7PQT7U7U V VWWXXXX Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y       $d $ $3:TBBBB""""   466 C CEEL KKMMM    sD AF2C>F& F2&F**F2-F*.F22 F?>F?'H== I r)r*r+r-r,reasonc tjtjtdt tdd5}|dtjdd|d d d d n #1swxYwYn#t$rYnwxYwtd |tj d d S) uRecord why the gateway subprocess is shutting down. Three exit paths (startup write fail, parse-error-response write fail, dispatch-response write fail, stdin EOF) all collapse into a silent sys.exit(0) here. Without this trail the TUI shows "gateway exited" with no actionable clue about WHICH broken pipe or WHICH message triggered it — the main reason voice-mode turns look like phantom crashes when the real story is "TUI read pipe closed on this event". Tr.r0r1r2u === gateway exit · r4u · reason=r5Nz[gateway-exit] r7) rr@rArBrrCrDrErFrQrRrOrS)rcr]s r _log_exitres  BGOOJ//$???? *cG 4 4 4  GG,7J)K)K,,#,,,                         $F $ $3:TBBBBBBs6AB/B  B BBBB B%$B%?timeoutcpt}||sdS||dS)aBriefly block until background MCP discovery finishes, up to ``timeout``. MCP discovery runs in a daemon thread spawned at startup (see main()) so a slow/dead server can't freeze ``gateway.ready``. But the agent snapshots its tool list ONCE at build time and never re-reads it, so a reachable-but- slow server that finishes connecting *after* the first prompt would be invisible for the whole session. Joining with a short bounded timeout before the first agent build lets already-spawning fast servers land without re-introducing the startup hang: a dead server simply isn't waited on beyond ``timeout``. No-op when no discovery thread was started. N)rg)_mcp_discovery_threadis_aliverM)rgthreads r wait_for_mcp_discoveryrls;#F ~V__..~ KKK     r ct ddlm}|pid}t |t ot |dk}n#t$rd}YnwxYw|r6dd}ddl}| |dd}| |a td d d d tid ds#tdtjdtjD]}|}|s t'j|}nN#t&j$r<td ddddds#tdtjdYywxYwt |t r|dnd} t-|} | 6t| s'td| dtjdtddS)Nr)read_raw_config mcp_serversTrc ddlm}|dS#t$r tddYdSwxYw)Nrdiscover_mcp_toolsz$Background MCP tool discovery failedT)exc_info)tools.mcp_toolrrrQloggerwarningrqs r _discover_mcp_backgroundz&main.._discover_mcp_backgroundsx ======""$$$$$   :T s &>>ztui-mcp-discovery)targetrLrUz2.0eventz gateway.readyskin)typepayload)jsonrpcmethodparamszO>ORS>S      ,     +***$+++$,  !, * 7OPP   PQQQ  yyy{{   *T""CC#   %6Vc:d:dlpqqrr RSSS H   '1d&;&;E"""}}  d## ]f]]]^^^  788888s%A A A-,A-D**AE54E5__main__r<)rf)*rrOrr _src_rootrAinsertrloggingr>rErG tui_gatewayr tui_gateway.serverrrrrtui_gateway.transportr getLogger__name__rurirr!r"r&r?rbhasattrr)SIG_IGNr*r+r-r,strrerlrrr r rs JNN3R 8 8  "#(**HOOAy!!! 7 6sx 6 6 6  MMMMMMMMMMMM......  8 $ $ 6 =====EEtEEEEl 7692FM&.&.111 769/FM&.+... 7680FM&----- WVZ  0FM&/;/// 7681FM&-000CcCdCCCC,!!E!T!!!!$Q9Q9Q9h zDFFFFFr