.cj~dZddlmZddlZddlZddlmZmZeje Z dZ dZ dd Z d dd ddZddZdS)uWake an existing agent session from a background completion event. Two delivery strategies, selected by the target adapter's ``supports_async_delivery`` capability flag: * Push-capable adapters (telegram, discord, plugin platforms, ...): inject a synthetic ``MessageEvent(internal=True)`` through ``adapter.handle_message`` — the pre-existing wake path, preserved exactly. * Stateless request/response adapters (the API server, ``supports_async_delivery = False``): ``handle_message`` would run the wake turn under a ``build_session_key()``-derived key (``agent:main:api_server:group:``) that NEVER matches the raw ``X-Hermes-Session-Id`` key real gateway/HQ turns run under (``_bind_api_server_session``), so the wake lands in a parallel, invisible session. Instead we self-POST ``/v1/chat/completions`` on the in-pod API server with the raw session id in the ``X-Hermes-Session-Id`` header — the exact entry point real turns use — so the wake turn resumes the REAL session, with full history, and its result is visible the next time the client polls/reopens the conversation. Failures RAISE (after bounded retries on transient errors) so callers can rewind cursors / retry instead of silently losing the event. ) annotationsN)AnyOptionalg@)g@g@g$@adapterrreturnboolc>tt|ddS)uWhether this adapter can push a message to the user after a turn ends. Mirrors ``gateway.session_context.async_delivery_supported`` but reads the capability off the adapter class (``supports_async_delivery``) instead of the request-scoped contextvar — background watchers run outside any bound session context. Adapters that don't declare the flag are push-capable. supports_async_deliveryT)rgetattr)rs ./home/ice/.hermes/hermes-agent/gateway/wake.pyadapter_supports_pushr -s !:DAA B BB) session_idsourcetextstrrrNonecKt|rJ|tdddlm}m}|||j|d}||d{VdS|stdt|||d{VdS) uDeliver a wake turn to the session behind ``adapter``. ``session_id`` is the RAW session id (the ``X-Hermes-Session-Id`` value / ``state.db`` key) — required for non-push adapters. ``source`` is the ``SessionSource`` used to build the synthetic event — required for push-capable adapters. Raises on failure (bad arguments, exhausted retries, HTTP error) so the caller can rewind/retry instead of treating the wake as delivered. Nz;deliver_wake: push-capable adapter requires a SessionSourcer) MessageEvent MessageTypeT)r message_typerinternalzudeliver_wake: non-push adapter (supports_async_delivery=False) requires the raw session id to self-post the wake turn)rr)r ValueErrorgateway.platforms.baserrTEXThandle_message_self_post_chat_completion)rrrrrr synth_events r deliver_waker 8s"W%% >M  EDDDDDDD"l$)    $$[111111111   E    %W4J O O OOOOOOOOOOrc TKddl}tt|ddpd}|dvrd}tt|ddpd}tt|d dpd}|st d d |vr|d sd |d }d|d |d}d||d}tt|ddpdd|dgdd} d} dt tz} t| D]} | r(tj t| dz d{V | t} | | 4d{V}||| |4d{V}|jdkrVt d|} t d| | dz|  dddd{Vdddd{V|jdkr?|d{Vdd }t d!|d"|jd#||d{Vt d$|| dz dddd{Vdddd{VdS#1d{VswxYwY dddd{Vn#1d{VswxYwY#|jtjt.f$r.}|} t d%|| dz| |Yd}~ d}~wwxYwt d&|d'| d(| | ))uPOST the wake text to the in-pod API server as a normal session turn. Uses the adapter's own bind host/port/key (``ApiServerAdapter.__init__``). Session continuation via ``X-Hermes-Session-Id`` is 403-gated on ``API_SERVER_KEY`` being configured, so a missing key is a hard error — raise loudly rather than run the wake in a fresh fingerprint-derived session nobody is looking at. rN_hostrz 127.0.0.1)z0.0.0.0z::*_porti!_api_keyzwake self-post requires API_SERVER_KEY: session continuation via X-Hermes-Session-Id is rejected (403) on an unauthenticated API server, so the wake cannot reach the target session:[]zhttp://z/v1/chat/completionszBearer ) AuthorizationzX-Hermes-Session-Id _model_namez hermes-agentuser)rolecontentF)modelmessagesstream)total)timeout)jsonheadersiz:wake self-post got HTTP 429 (concurrency cap) for session z%s; attempt %d/%dii,z"wake self-post failed for session z: HTTP z: z4wake self-post delivered for session %s (attempt %d)zCwake self-post transient failure for session %s (attempt %d/%d): %sz#wake self-post gave up for session z after z attempts: )aiohttprr int RuntimeError startswithlen_RETRY_DELAYS_SECONDSrangeasynciosleep ClientTimeoutWAKE_TURN_TIMEOUT_SECONDS ClientSessionpoststatusloggerwarningrreadinfo ClientError TimeoutErrorOSError)rrrr6hostportapi_keyurlr5payloadlast_errattemptsattemptr3httprespbodyexcs r rrasNNN ww,,; < J; ?KL #L  L)rrrr) rrrrrrrrrr)rrrrrrrr)__doc__ __future__rr=loggingtypingrr getLogger__name__rDr@r;r r rrr r^s2#"""""  8 $ $" )CCCC &P&P&P&P&P&PRWWWWWWr