+ jHjZRt^RIHt^RIt^RIt^RIt^RIt^RIt^RIt^RI t ^RI t ^RI t ^RI Ht]P!R4t]P"!R4tRtR@tRRltR R ltR tR R ltRRltRRltRRltRRltRRltRRltRRltRRlt RRlt!R R!lt"R"R#lt#R$R%lt$R&R'lt%R(R)lt&R*R+lt'R,R-lt(RAR.R/llt)R0RR1RR2RR3]/R4R5llt*R6R7lt+R8R9lt,R3]/R:R;llt-R<R=lt.RBR>R?llt/R#)CaRelay/connector support package for the Hermes gateway. EXPERIMENTAL gateway side of the "Gateway Gateway" relay design: a generic ``RelayAdapter`` plus the wire-serializable ``CapabilityDescriptor`` the connector hands it at handshake, and the production ``WebSocketRelayTransport``. The public API MAY CHANGE without a deprecation cycle until >=2 real Class-1 platforms have shaken out the schema (``website/docs/developer-guide/relay-connector-contract.md``). Activation is config-driven: the relay platform is registered when a connector relay URL is set (``GATEWAY_RELAY_URL`` env or ``gateway.relay_url``), like ``gateway.proxy_url``, unless the effective relay platform configuration explicitly disables it. ) annotationsN)Optionalz gateway.relayz9[A-Za-z0-9_-]+(?:\.[A-Za-z0-9_-]+){2,}|[A-Za-z0-9_-]{32,}g.@cV^8dQhRR/#returndict)formats";/home/ubuntu/.hermes/hermes-agent/gateway/relay/__init__.py __annotate__r .s0040cx^RIHpV!4p\T\4'dT#/# \d/u#i;i)uRThe full gateway config, or ``{}`` — config absence/parse must never crash boot.)_load_gateway_config) gateway.runr Exception isinstancer)rcfgs r _load_cfgr.sA4"$S$''3/R/  s ) 99cV^8dQhRR/#rr )r s"r r r 9s44d4r ch\4PR4p\V\4'dV#/#)z1The ``gateway:`` block of config.yaml, or ``{}``.gateway)rgetrr)blocks r _gateway_cfgr9s) KOOI &Eud++533r c^RIHpV!4'g\P!4#^RIHp^RIHpV!V!44#)aThe launch profile's runtime scope once the gateway multiplexes, ``nullcontext`` before. Self-provision runs at startup, before any turn binds a profile, and under multiplexing the Nous Portal and inference routing overrides only resolve inside a profile scope. The scope is built from the profile's files like a turn's (``gateway.run._profile_runtime_scope``), not via ``launch_profile_scope_if_multiplexed``, whose first entry freezes the launch env snapshot before startup has written ``GATEWAY_RELAY_*`` into ``os.environ``. )is_multiplex_active)_profile_runtime_scope)get_process_hermes_home)agent.secret_scoper contextlib nullcontextrrhermes_constantsr)rrrs r _launch_profile_scoper#?s47  %%''28 !"9"; <``; stripped, ``""`` when unset.)osenvironrstripr&r)r%r'values&& r _env_or_cfgr.RsR JJNN7B ' - - /E  F FC **7B7==2>DDFFr c$V^8dQhRRRRRR/#)rr%r&r'r Optional[str]r )r s"r r r Xs!==S=3===r cJ\W4PR4;'gR#)zP``_env_or_cfg`` for URL-shaped values: trailing slash stripped, None when unset./N)r.rstrip)r%r's&&r _env_or_cfg_urlr4Xs w ( / / 4 < <rrrrRELAY from_dictenabled) r9r:r;r<r=r>rrr?rs r relay_explicitly_disabledrH]s8ll001 c4 $.swwy/A4$H$Hcggi bG'b9I[[%=r9~~N^_ MM' "E eT " "%))GR*@*D*DEX*Y*Y''.66 66 s D D#"D#cV^8dQhRR/#rrr0r )r s"r r r zs====r c>\4'dR#\RR4#)zMEffective connector URL; an explicit platform disable vetoes even an env URL.NGATEWAY_RELAY_URL relay_url)rHr4r r r rMrMzs "" . < ``(None, None)`` and the transport dials unauthenticated.GATEWAY_RELAY_IDrelay_idGATEWAY_RELAY_SECRET relay_secretNr.) gateway_idsecrets r relay_connection_authrws7/The gateway's own PUBLIC inbound URL, asserted to the connector at provision (``GATEWAY_RELAY_ENDPOINT`` / ``gateway.relay_endpoint``). Stored on the tenant's route rows; gateway-asserted but tenant-scoped, so a dishonest gateway can only misdirect its OWN inbound. Absent -> outbound-only (no inbound routes written).GATEWAY_RELAY_ENDPOINTrelay_endpointr4r r r r|r| 35E FFr cV^8dQhRR/#)rr list[str]r )r s"r r r s < <)  tenant, endpoint), so keys only take effect alongside ``relay_endpoint()``. ``GATEWAY_RELAY_ROUTE_KEYS`` is comma-separated; ``gateway.relay_route_keys`` may be a list or a comma string.GATEWAY_RELAY_ROUTE_KEYSr)relay_route_keysrQ) r*r+rr,rrlisttupler&rS)rivalks r rrs **..3R 8 > > @C n  !3R8 cD%= ) ),/BCq3q6<<>NCFLLNCB B#))n""$"yy~ ;~!IAGGI~ ;;C ;s1!D D -D% D%cV^8dQhRR/#rJr )r s"r r r sQQ=Qr c.\RR4;'gR#)a<Stable per-instance id forwarded at provision (``GATEWAY_RELAY_INSTANCE_ID`` / ``gateway.relay_instance_id``): binds the connector's ``gatewayId -> instanceId`` so inbound routes per-instance rather than tenant-broadcast (NAS stamps its ``AgentInstance.id``). Tenant-scoped like ``relay_endpoint()``; absent -> null.GATEWAY_RELAY_INSTANCE_IDrelay_instance_idNrtr r r rrs 24G H P PDPr cV^8dQhRR/#rJr )r s"r r r ryr c\RR4#)a0The gateway's WAKE URL forwarded at provision (``GATEWAY_RELAY_WAKE_URL`` / ``gateway.relay_wake_url``): a payload-free poke the connector GETs when a going-idle destination receives its first buffered event, so a suspended gateway wakes, reconnects and drains. Absent -> no wake (buffering still works).GATEWAY_RELAY_WAKE_URLrelay_wake_urlr}r r r rrr~r cV^8dQhRR/#rJr )r s"r r r sMr cJ\PPRR4P4pV'gI^RIHp\ V!4PRR4;'gR4P4pVR8XdRpVR,;'gR# \dRpL+i;i)u3The human-facing agent display name forwarded at provision — the connector's multi-agent reply-attribution prefix (``**:** ``). ``GATEWAY_RELAY_DISPLAY_NAME`` env, then the skin's branded agent name (a skin rename propagates on the next boot). Absent -> connector's linked-owner fallback. The PRIMARY source for the connector's multi-agent reply-attribution prefix (gateway-gateway #171): in a multi-agent scope the shared bot prepends ``**:** `` to this instance's replies. Gateway-asserted but safely scoped exactly like ``relay_instance_id()`` / ``relay_wake_url()`` — the tenant stays token-verified, so a dishonest gateway can only label its OWN instance. Absent -> the connector stores null and attribution falls back to the instance's linked-owner identity, else skips the prefix. GATEWAY_RELAY_DISPLAY_NAMEr))get_active_skin agent_namez Hermes Agent:N@NN) r*r+rr,hermes_cli.skin_enginerr& get_brandingr)r-rs r relay_display_namers JJNN7 < B B DE   >)66|RHNNBOUUWE N "E :   E s(B!B B"!B"c$V^8dQhRRRRRR/#)rrelay_dial_urlr&pathrr )r s"r r r s!5535c5c5r c&^RIHpV!V4 V 2#)uJ``ws(s)://…/relay`` dial URL -> ``http(s)://…{path}`` connector route.)media_base_url)gateway.relay.mediar)rrrs&& r _connector_urlrs2^, -dV 44r c V^8dQhRRRR/#)rrr&rr )r s"r r r s>>3>3>r c\VR4#)z/relay/provision)r)rs&r _provision_urlrs .*< ==r c(V^8dQhRRRRRRRR/#)rurlr&tokenbodyrtimeoutfloatr )r s"r r r s( 8 8C 8 84 8% 8r c \PPV\P!V4P R4RRRV 2RRRR/R7p\PP WCR 7#) zLBearer-authenticated JSON POST; returns the open response (caller reads it).utf-8POST AuthorizationzBearer Content-Typeapplication/jsonAcceptdatamethodheadersr)urllibrequestRequestredumpsencodeurlopen)rrrrreqs&&&& r _json_postr so ..  ZZ  $ $W - wug. . ( ! C >> ! !# ! 77r c V^8dQhRRRR/#)rrYr0rzOptional[dict]r )r s"r r r s;;];n;r cFaa Sf\4wopS'dSR8XdR#Rp.p\4o V V3Rlp\RV!44/4pRV9dVPR4pM$S PR4eS PR4pVPR4pVfS PR4p\ V\ \ 34'dKVUu.uF=p\V4P4'gK$\V4P4NK? ppMq\ V\4'd\VP4'dFVPR4Uu.uF*qwP4'gKVP4NK, pp\PPSP4 R2R 4P4P4pVR9p VfV'g V 'gR#R SR \V4R VR V /#uupiuupi \dLi;i)aqProject a fronted platform's RELEVANCE config into the connector's generic vocabulary. The connector's relevance gate reasons over a platform-agnostic policy keyed by ``(tenant, platform, instanceId)``: ``requireAddress`` <- ``require_mention``, ``freeResponseScopes`` <- ``free_response_channels``, ``allowOtherBots`` <- ``{PLATFORM}_ALLOW_BOTS`` in {"mentions","all"}. Read from the platform's config block (``discord:``), falling back to the bridged top-level keys, then env. ``platform`` defaults to the PRIMARY fronted platform. Returns None when relay isn't configured or nothing is CONFIGURED to declare, so the connector's default (mention-gated) applies. The condition is "require_mention is unset", NOT "falsy": an EXPLICIT ``require_mention: false`` is a non-default choice that MUST be declared or the connector would mention-gate an agent configured to free-respond. Nr@c3L<"SPS4xSPR4;'g/PR4;'g/p\V\4'dVPS4MRxSPR4;'g/PS4xR#5i)rr?N)rrr) gw_platformsrrYs r _candidates+relay_relevance_policy.._candidates3s''(# #GGI.44"99+FLL"L0:<0N0N,""8,TX X77;'--2228< )relay_relevance_policy..9sIMqZ45HMs) )require_mentionfree_response_channelsrQ _ALLOW_BOTSr)rYrequireAddressfreeResponseScopesallowOtherBots>allmentions)rmrnextrrrrr&r,rSrr*r+upperlowerr7) rY_bot_idr free_responserplat_cfgfrcrallow_bots_envallow_other_botsrs f @r relay_relevance_policyrs35' x7*O!M k = IKMI2N  (&ll+<=O WW& ' 3!gg&78Oll34 ;''23C cD%= ) )58KSCFLLN^SV\\^SMKM S ! !ciikk03 #L1'')YQWWYML ZZ^^x~~'7&8 $DbIOOQWWYN%)<<}=MH$/m*  LL    sHB,H!H<HH+HHH 7H  H H H H  instance_idwake_url display_namercHV^8dQhRRRRRRRRRRRRR R R RR RR RRRRR/ #)r provision_urlr& access_tokenrurYr[gateway_endpointr0 route_keysrrrrrrrrr )r s"r r r XsHHHH H  H  H$HHHH HH Hr c RTRTRTRT;'gRRV/p RV3RV3R V 33FwrV 'gKWV &K \WW4;_uu_4p\P!VP4P 44pR R R 4\X\4'g \R4hTPR4'g!TPR4RJd \R4hT# +'giLj;i \ P PdpRp\P!TP4P 44;'g/PR R4pM \dMi;i\R TP 2T'dR T 2,4ThR,4ThR p?i\ P Pdp\RTP 24ThR p?ii;i)a-POST ``/relay/provision``; return ``{secret, deliveryKey, tenant, gatewayId, routeKeys}`` (the connector validates ``access_token`` against NAS, derives the tenant, mints the per-gateway secret and upserts route rows). Raises RuntimeError with a user-facing message on any non-2xx / transport failure. gatewayIdrYrRgatewayEndpointr) routeKeys instanceIdwakeUrl displayNameNerrorzconnector returned HTTP z: could not reach connector: z)connector returned an unexpected responserv secretIssuedFz5connector returned an unexpected response (no secret))rrerfreaddecoderr HTTPErrorrr RuntimeErrorcodeURLErrorreasonrr)rrrurYr[rrrrrrrkeyr-resppayloadexcdetails$$$$$$$$$$$ r _post_provisionrXs& ZH+11rZ D%k2Y4IM[gKhi  5Ij P  T C Ctjj!3!3!56GD gt $ $FGG& ;;x W[[%@%M RSS NSD C << ! ! jj!2!2!45;;@@"MF   &sxxj 1fr&] U  RT U   << P8 EFCOPslC63C#C6# C3 .C63C66G.F.A E%$F.% E30F.2E33;F.. G.G.G))G.cV^8dQhRR/#)rrr&r )r s"r r r sX X sX r c 4a\Uu/uFBq\PPRVP 4 2R4P 4bKD upoSR,'g\ 4PR4p\V\4'dTM/p\FJpSV,;'g4\VPVR4;'gR4P 4SV&KL V3Rl\4wr#rEV'g+^RI H p\4;_uu_4V!4uuRRR4#V'Eg2V'Eg)\PPVRR R /R 7p\PP!V\"R 7;_uu_4pVP%4P'4P 4p RRR4Rp X P)R 4'dX\*P,!V 4;'g/PR4p \V \4'dV P 4p M\0P3V 4'dT p V 'g \5R4hV #V'd V'gV'dRMRp \5RV R24hRRRVRV/p V'dW]R&\PPV\P6P9V 4P;R4RRRR R/R7p\PP!V\"R 7;_uu_4p\*P,!VP%4P'44pRRR4X;'g/PR4p\V\4'dVP 4'g \5R4hVP 4#uupi +'giEL;i +'giEL(;i \.dRp ELi;i +'giL;i)aResolve the caller-identity bearer token the connector introspects to a tenant. Canonical resolver shared by runtime self-provision and ``hermes gateway enroll``. Modes, in precedence order: 1. Generic OIDC client-credentials (self-hosted IdP): ``gateway.idp.token_url`` (``GATEWAY_RELAY_IDP_TOKEN_URL``) set together with client id + secret -> POST the OAuth2 ``client_credentials`` grant. 1b. Ambient token endpoint: ``token_url`` with NEITHER client_id nor client_secret is a metadata-server-style endpoint (e.g. Domino's ``$DOMINO_API_PROXY/access-token``): a plain GET whose body IS the token, raw JWT or a JSON envelope with ``access_token``. Possession of the (typically loopback) endpoint is the credential. 2. Nous Portal (default): ``resolve_nous_access_token()``. Raises on failure; callers decide whether that's fatal (enroll CLI) or a graceful boot no-op (self-provision). GATEWAY_RELAY_IDP_r) token_urlidpc36<"TFpSV,xK R#5irr )rrenvs& r r0_resolve_relay_identity_token..s1L)Q#a&&)s)resolve_nous_access_tokenNGETrzapplication/json, text/plain)rrr{rzno client_id/client_secret configured, so gateway.idp.token_url was treated as an ambient token endpoint (GET), but the response body was not a token. For the OAuth2 client_credentials grant, configure client_id and client_secret alongside token_url. client_secret client_idzFgateway.idp.token_url is configured with a partial client credential (z missing). Configure both client_id and client_secret for the OAuth2 client_credentials grant, or neither to treat token_url as an ambient token endpoint (plain GET returning the token). grant_typeclient_credentialsscoperrrz!application/x-www-form-urlencodedrrz3IdP client_credentials response had no access_token) _IDP_KEYSr*r+rrr,rrrr&hermes_cli.authrr#rrrr_HTTP_TIMEOUT_Srr startswithrerf ValueError_AMBIENT_TOKEN_SHAPE fullmatchrparse urlencoder)rrrrrr rrrrrenvelope_tokenmissingformrrrs @r _resolve_relay_identity_tokenrsH$U^ ^T]qbjjnn1!'')=rBHHJ JT] ^C {  n  'T**cAV@@s3771b>#7#7R8>>@CF1L)1L.I- =# $ $,.% $ 9]]nn$$ eh8V-W% ^^ # #C # A AT99;%%'--/DB ??3   &"&**T"2"8"8b!=!=n!M .#..&,,. ! + +D 1 1EC   M&//KyL M   . YYf gD W ..  ..t4;;GDV!DhPbc ! C   _  = =**TYY[//12 >MMr&&~6L lC ( ( 0B0B0D0DPQQ    M _% $ $B A A  &!% &H > =sBAOO -O"O3?O3)3P O  O0 3 PP P cV^8dQhRR/#r6r )r s"r r r srrdrr c2\4pV'gR#\4wrV'd V'd\PR4R#\ 4p\4p\P!4P4p\PPRR4P4;'gRT;'gR 2p\4p\4p \!4p \#4p \%4p .p /pTEFwpp\'\)T4TYTTYT T R 7 pT P-T4TPR 4'gKN\PPR 4'dKu\/TPR 4;'gT4\PR&\/TR ,4\PR &\/TPR4;'gR4\PR&EK T 'g/\P RRP1RT444R#\PPR 4'g)\P RRP1T 4T4R#\PR\PPRT4\/TPR4;'gR4;'gRRP1T 4\3T 4T'dRMRT ;'gRT 'dRMR4R# \ d"p\P RT4Rp?R#Rp?ii;i \ dRpELi;i \*d#p\P R Y4Rp?EKRp?ii;i)aBoot-time relay self-provision: mint relay creds in-process, no human, no disk. Fires when ``relay_url()`` is set and NO per-gateway secret is pinned: resolves the identity token, POSTs ``/relay/provision`` for EACH fronted platform and sets ``GATEWAY_RELAY_ID`` / ``_SECRET`` / ``_DELIVERY_KEY`` in ``os.environ`` for ``register_relay_adapter()``. Creds live ONLY in process memory (never ``~/.hermes/.env``), so a hosted container re-provisions every boot; the connector's rotation window covers a still-connected prior instance. The trigger is deliberately NOT ``is_managed()`` (False on a NAS-hosted Fly agent): "pointed at a connector without a pinned secret" is the real signal and self-guards (an enrolled gateway has a PINNED secret -> skipped; no resolvable identity -> no-op). Returns True iff it provisioned. NEVER raises: a failure logs and returns False so the gateway still boots (the adapter then dials unauthenticated / is rejected). Fz>relay self-provision skipped: GATEWAY_RELAY_SECRET already setzCrelay self-provision skipped: could not resolve identity token (%s)Nr)rpzgw-hermes) rrrurYr[rrrrrzJrelay self-provision failed for platform=%s (%s); continuing with the restrvrrr deliveryKeyGATEWAY_RELAY_DELIVERY_KEYzXrelay self-provision failed for ALL platforms (%s); gateway will boot without relay authrQc3*"TF wrVxK R#5irr )rrVr`s& r r'self_provision_relay..Rs.:41Q:szrelay self-provision withheld credentials for ALL platforms (%s): the connector holds a binding for gateway_id=%s this caller could not prove ownership of; gateway will boot without relay auth. Recover with POST /relay/rotate or pin GATEWAY_RELAY_SECRETzfrelay self-provisioned (gateway_id=%s tenant=%s platforms=%s routes=%d inbound=%s instance=%s wake=%s)tenant?yesz outbound-onlyunboundnoneT)rMrwrginforrrhr\socket gethostnamer,r*r+rr|rrrrrrrrUr&joinlen)dial_url existing_idexisting_secretrr identitieshostruendpointrrrr provisionedresultrYr[s r self_provision_relayr0s{H #8#: K TU46 +,J!!#))+ 2B7==?[[SIYIYQYHZC[JH!#J#%KH%'L KF&& $,X6\%Zb%) F 8$ ::h   7M(N(N-0K1H1V1VJ-WBJJ) *14VH5E1FBJJ- .7:6::m;T;Z;ZXZ7[BJJ3 4;'>  f HH.:. .  ::>>0 1 1  # HH[ !:   KKp ):6 FJJx & &B'..3  J  yv  q \^ab 0  NN\    sB L&#MM)& M1M  M M&%M&) N4NNc ,V^8dQhRRRRRRRRRR /#) r policy_urlr&rpolicyrrrrintr )r s"r r r ss7 P P PC P P Pdg Pr c\WW#4;_uu_4p\VP4uuRRR4# +'giR#;i \PP d p\TP 4uRp?#Rp?i\PPdp\RTP 24ThRp?ii;i)aPOST the relevance policy to ``/relay/policy``; return the HTTP status. Authenticated with the gateway's own upgrade token, so the connector resolves ``{tenant, instanceId}`` from its stored secret record, never the body. Raises RuntimeError on transport failure.Nr) rr4statusrrrrrrr)r2rr3rrrs$$$$ r _post_policyr7ss P  6 ; ;tt{{#< ; ; ; << ! !388} << P8 EFCOPsIA 6 A A A A C)B=C C$C%B>>CcV^8dQhRR/#r6r )r s"r r r s7747r c \4pV'gR#\4wrV'd V'gR#^RIHpV!W4p\TR4pRp\4Fwr\T4p T fK\YdT R7p T ^8XdmRp\ PR T PR 4T PR 4\T PR 4;'g.4T PR 44K\ P RTT 4K T# \d"p\ P RT4Rp?R#Rp?ii;i \d#p\ P RY4Rp?EK Rp?ii;i)aDeclare this gateway's relevance policy to the connector, per fronted platform, at boot AFTER the per-gateway secret is resolved. The connector enforces it on delivery, so the SAME mention-gating / free-response / allow-bots behavior the agent applies directly also governs relay delivery, and excluded traffic never wakes a scaled-to-zero agent. Re-declared every boot (idempotent full replace); a platform with nothing non-default is skipped; one failed POST doesn't block the others. NEVER raises / blocks boot: relevance is an optimization layered on the authorization gate, so a failure just leaves the connector's prior policy. Returns True iff the connector accepted at least one policy (HTTP 200).F)make_upgrade_tokenzQrelay policy declaration failed to build token (%s); connector keeps prior policyNz /relay/policy)r2rr3z@relay policy declaration failed for platform=%s (%s); continuingTzSrelay policy declared (platform=%s require_address=%s free_scopes=%d allow_bots=%s)rYrrrz_relay policy declaration for platform=%s returned HTTP %s; connector keeps prior/default policy)rMrwgateway.relay.authr:rrgrhrr\rr7r#rr') r(rurvr:rrr2 any_declaredrYrr3r6s r send_relay_policyr=sF{H .0J V9":6  /:JL68'1 >  !ZVTF S=L KKe :& +,FJJ34::; +,   NNq +94 A jlop  NNRT\    s/D1 D= D:D55D:= E*E%%E*c$V^8dQhRRRRRR/#)rforcer7rr0rr )r s"r r r s!??$?]?d?r c aaaaa a \4'dR#VeTM \4o V'g S 'gR#^RIHpHp^RIHo^RIHoH o\4wo oVVVVV V 3RlpVPV!RRVRR R R 74R #) aURegister the generic ``relay`` platform when a relay URL is configured (or ``force=True`` for tests: transport-less adapter). Neither overrides an explicit profile disable. Returns True if registered. With a URL the factory builds a live ``WebSocketRelayTransport``; the adapter negotiates the real ``CapabilityDescriptor`` at ``connect()``.F) PlatformEntryplatform_registry) RelayAdapter)CONTRACT_VERSIONCapabilityDescriptorc <S!SS RRRRRRRR7 pRpS 'd*^RIHp\4wrEV!S S S \4VVRR 7pS!WVR 7#) RelayiFTplainchars) contract_versionrYlabelmax_message_lengthsupports_draft_streaming supports_editsupports_threadsmarkdown_dialectlen_unitN)WebSocketRelayTransport)r+ruupgrade_secret reconnect) transport)gateway.relay.ws_transportrRrwr\) config placeholderrUrRrurSrDrErCr[rY resolved_urls & r _factory(register_relay_adapter.._factorysw+-#%*"$    J)>)@ &J/56%- IF9EEr r@rGcR#)Tr r r r (register_relay_adapter..sTr builtinu🔌)namerKadapter_factorycheck_fnsourceemojiT) rHrMgateway.platform_registryrArBgateway.relay.adapterrCgateway.relay.descriptorrDrErmregister) r?rrArBrZrDrErCr[rYrYs && @@@@@@r register_relay_adapterrisx !""/3y{L \J2O.0Hf!F!FF$!    r )rrrr r)FN)0__doc__ __future__rr reloggingr*rer$ urllib.errorr urllib.parseurllib.requesttypingr getLoggerrgcompilerr r rrr#r.r4rHrMr\rarTrmrwr|rrrrrrrrrrr0r7r=rir r r rts2 #     ? + zz  A 04 =&G = 7:=$G * 0G <QGD5> 8;|H"&H#H#'H%HVX vrj PP_ P7t??r