(Gj UdZddlmZddlZddlmZddlmZejZ da da de d<dd Z ddZddZddZdddZddZdddZdS) z9Shared CLI/TUI-safe helpers for background MCP discovery.) annotationsN) nullcontext)OptionalFzOptional[threading.Thread]_mcp_discovery_threadreturnboolc ddlm}|pid}t|tot |dkS#t $rYdSwxYw)zBCheap config probe so non-MCP users avoid importing the MCP stack.r)read_raw_config mcp_serversT)hermes_cli.configr get isinstancedictlen Exception)r r s ._discover&sZ T=????? T T T Cd SSSSSS Ts !88)targetnamedaemonrr)_mcp_discovery_lock_mcp_discovery_startedr threadingThreadrstart)rrrthreads` rstart_background_mcp_discoveryr(s>  !  "&*,,    T T T T T T !    !' 's A=A=3A==BBexplicit'float | None'floatc||S ddlm}m}t|dd}|pid|}t|}|dkr|n|S#t $rYdSwxYw)uyResolve the MCP discovery wait bound: explicit arg > config > default. Reads ``mcp_discovery_timeout`` from config.yaml, defaulting to the value in ``DEFAULT_CONFIG`` (single source of truth) when the key is absent. Kept lazy and fail-safe — a missing/invalid value or a broken config falls back to a short safe bound so startup can never hang or crash. Nr) load_configDEFAULT_CONFIGmcp_discovery_timeoutg?)r r-r.r+r r)r)r-r.defaultrawvals r_resolve_discovery_timeoutr35sAAAAAAAA**+BCHHII{}}"''(?IICjjAggss7* sssA#A** A87A8c ddlm}n#t$r t}YnwxYw|5ddlm}|ddddS#1swxYwYdS)zCRun MCP discovery without letting OAuth read from the user's stdin.r)suppress_interactive_oauth)discover_mcp_toolsN)tools.mcp_oauthr5rrtools.mcp_toolr6)r5r6s rrrJs1>>>>>>> 111%0"""1 $ # % %555555s AA A timeoutct}||sdS|t|dS)uWait for background MCP discovery before the first tool snapshot. ``thread.join(timeout)`` returns the INSTANT discovery completes, so this only ever blocks for the real connect time of a still-pending server — users with no MCP servers or fast servers pay ~0s. The bound (from ``mcp_discovery_timeout`` in config) just caps the wait so a dead server can't freeze startup; servers that miss it are picked up by the automatic late-binding refresh. Nr9)ris_alivejoinr3r9r's rwait_for_mcp_discoveryr?WsD#F ~V__..~ KK27;;K<<<<<c@t}|duo|S)a5Return True if THIS module's background discovery thread is still running. Mirrors ``tui_gateway.entry.mcp_discovery_in_flight`` for the surfaces that start discovery through ``start_background_mcp_discovery`` here (the desktop app + dashboard WebSocket sidecar via ``tui_gateway/ws.py``, and ``hermes dashboard``). Those processes populate THIS module's ``_mcp_discovery_thread``, not ``tui_gateway.entry``'s, so the late-refresh scheduler must consult both to decide whether a slow server's tools are still pending (see #51587). N)rr<)r's rmcp_discovery_in_flightrBgs##F   3&//"3"33r@cnt}|dS||| S)alBlock until THIS module's background discovery finishes, up to ``timeout``. Returns True if discovery has completed (thread absent or no longer alive), False if it is still running after the timeout. Unlike ``wait_for_mcp_discovery`` this accepts an unbounded/long wait and reports the outcome, for the off-critical-path late-refresh waiter. NTr;)rr=r<r>s rjoin_mcp_discoveryrDvs:#F ~t KKK      r@)rr)rrrr)r)r*rr+r!)N)r9r*rr)r9r*rr)__doc__ __future__rr$ contextlibrtypingrLockr"r#r__annotations__rr(r3rr?rBrDr@rrLs???""""""""""""$in&&488888    4*     = = = = = 4 4 4 4 ! ! ! ! ! ! !r@