+ ~j ^RIHt^RIt^RIt^RIHtHt^RIt^RIH t ].]P3,t ]P] R,,!R4t RRltRR ltR R lt]P"R R l4tR#)) annotationsN) AsyncIteratorCallable)loggeragent_http_sessioncV^8dQhRR/#)return_ClientFactory)formats"v/Users/mitch_tango/dev/rabbit-r1-livekit/agent/.venv/lib/python3.14/site-packages/livekit/agents/utils/http_context.py __annotate__rs.cHaRoRV3Rllp\PV4V#)NcV^8dQhRR/#r r zaiohttp.ClientSessionr )r s"rr&_new_session_ctx..__annotate__s/rc(<SeSP'dh\P!R4^RIHpV!4P P p\P!^2^xR7p\P!WR7oS# \dRpL@i;i)Nz-http_session(): creating a new httpclient ctx)get_job_context)limit_per_hostkeepalive_timeout)proxy connector) closedrdebugjobrproc http_proxy RuntimeErroraiohttp TCPConnector ClientSession)rrr g_sessions r _new_session&_new_session_ctx.._new_sessions   0 0 0 LLH I - ",.33>>  ,,!"%I --JTI  "!  "sB BB) _ContextVarset)r%r$s @r_new_session_ctxr)s&.2I&OOL! rcV^8dQhRR/#rr )r s"rrr)s  + rcX\PR4pVf \R4hV!4#)zOptional utility function to avoid having to manually manage an aiohttp.ClientSession lifetime. On job processes, this http session will be bound to the main event loop. NaAttempted to use an http session outside of a job context. This is probably because you are trying to use a plugin without using the agent worker api. If you're running plugins outside the agent worker (e.g. tests or scripts), wrap your code with `async with livekit.agents.utils.http_context.open(): ...`. Alternatively, create your own aiohttp.ClientSession, pass it into the plugin constructor as a kwarg, and manage its lifecycle.)r'getr vals r http_sessionr/)s3 //$ C { N  5LrcV^8dQhRR/#)r r Noner )r s"rrr9strc"\PR4pVeK\P!R4V!4P 4GRjxL \P R4R#R#L5i)Nz*http_session(): closing the httpclient ctx)r'r,rrcloser(r-s r_close_http_ctxr49sJ //$ C  ABekkmsAA* A( A*cV^8dQhRR/#)r r z$AsyncIterator[aiohttp.ClientSession]r )r s"rrrBs  8 rc"\PR4e\P4!45xR#\4pV!45x\4GRjxL R#L \4GRjxL i;i5i)uvBind a process-local aiohttp.ClientSession to the current asyncio context. Use this when running plugins outside a job worker (e.g. tests, scripts, notebooks) so that ``http_session()`` returns a usable session inside the ``async with`` block. The session is closed and the context is reset on exit. If an http session context is already bound (nested call, or already set up by the worker), this is a no-op pass-through — the existing session is yielded and left untouched on exit. Example:: async with utils.http_context.open(): async with AgentSession() as session: await session.start(MyAgent()) N)r'r,r)r4)factorys ropenr8AsU$t(oo!! G ios6AA; A# A;A!A;#A81A42A88A;) __future__r contextlib contextvarscollections.abcrrr!logrr#r ContextVarr'r)r/r4asynccontextmanagerr8r rrr@sp"3"g3334$$^d%:;