`gj UdZddlmZddlZddlmZddlmZejZ da da de d<dd Z dd Zdd Zdd Zddd ZddZdddZy)z9Shared CLI/TUI-safe helpers for background MCP discovery.) annotationsN) nullcontext)OptionalFzOptional[threading.Thread]_mcp_discovery_threadc ddlm}|xsijd}t|txrt |dkDS#t $rYywxYw)zBCheap config probe so non-MCP users avoid importing the MCP stack.r)read_raw_config mcp_serversT)hermes_cli.configrget isinstancedictlen Exception)rr s I/root/.hermes/venv/lib/python3.12/site-packages/hermes_cli/mcp_startup.py_has_configured_mcp_serversrsR5&(.B33MB +t,E[1AA1EE s?A A Act5tr dddydats dddydfd }tj||d}|a|j dddy#1swYyxYw)zBSpawn one shared background MCP discovery thread for this process.NTc` ty#t$rjddYywxYw)Nz$Background MCP tool discovery failedT)exc_info)-_discover_mcp_tools_without_interactive_oauthrdebug)loggersr _discoverz1start_background_mcp_discovery.._discover&s1 T=? T Cd S Ts --)targetnamedaemonreturnNone)_mcp_discovery_lock_mcp_discovery_startedr threadingThreadrstart)r thread_namerthreads` rstart_background_mcp_discoveryr&sz  ! "&*,   T !!  !' 'sA( A(0A((A1c||S ddlm}m}t|j dd}|xsij d|}t|}|dkDr|S|S#t $rYywxYw)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. r) load_configDEFAULT_CONFIGmcp_discovery_timeoutg?)r r(r)floatr r)explicitr(r)defaultrawvals r_resolve_discovery_timeoutr05suA**+BCHI}"''(?ICjAgs*7* sAAA A$#A$c ddlm}|5ddlm}|dddy#t$r t}Y/wxYw#1swYyxYw)zCRun MCP discovery without letting OAuth read from the user's stdin.r)suppress_interactive_oauth)discover_mcp_toolsN)tools.mcp_oauthr2rrtools.mcp_toolr3)r2r3s rrrJsL1> $ %5 1%0"1s&;88Aclt}||jsy|jt|y)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. Ntimeout)ris_alivejoinr0r8r%s rwait_for_mcp_discoveryr<Ws.#F ~V__. KK27;K<c:t}|duxr|jS)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)rr9)r%s rmcp_discovery_in_flightr?gs #F   3&//"33r=cZt}|y|j||j 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. Tr7)rr:r9r;s rjoin_mcp_discoveryrAvs/#F ~ KKK   r=)rbool)r$strrr)r,'float | None'rr+r)N)r8rDrr)r8rDrrB)__doc__ __future__rr! contextlibrtypingrLockrr r__annotations__rr&r0rr<r?rAr=rrLsX?""$inn&4818 4*  = 4 !r=