+ LV-jhJ^RIHtHtHtHtHtHtHtHtH t H t ^RI H t H t HtHtHtHtHt^RIHtHtHt^RIHtHt^RIHt^RIHtHtHtH t H!t!H"t"H#t#H$t$H%t%H&t&^RI'H(t(H)t)H*t*^RI+H,t,H-t-.ROt.!R R ]*]*R 7t/!RR ]*]*R 7t0Rt1RRlt2RRlt3!RR 4t4R#)) AnyCallablecastDictListOptionaloverloadTupleTypeUnion)ConnectionClosedData EndOfMessageEventInformationalResponseRequestResponse)get_comma_headerhas_expect_100_continueset_comma_header)READERS ReadersType) ReceiveBuffer) _SWITCH_CONNECT_SWITCH_UPGRADECLIENTConnectionStateDONEERRORMIGHT_SWITCH_PROTOCOL SEND_BODYSERVERSWITCHED_PROTOCOL)LocalProtocolErrorRemoteProtocolErrorSentinel)WRITERS WritersType Connection NEED_DATAPAUSEDc]tRt^3tRtR#)r*N__name__ __module__ __qualname____firstlineno____static_attributes__r-`/Volumes/fast/ai/experiments/ui-tars-smoke/.venv/lib/python3.14/site-packages/h11/_connection.pyr*r*3r4) metaclassc]tRt^7tRtR#)r+r-Nr.r-r4r5r+r+7r6r4cRV^8dQhR\\\3,R\/#eventreturn)r rrbool)formats"r5 __annotate__r@Ts$uWh./Dr4cl\VPR4pRV9dR#\VRR4R8dR#R#) connectioncloseF http_version1.1T)rheadersgetattr)r< connections& r5 _keep_aliverITs4!%--?J:unf-6 r4c V^8dQhR\R\\\3,R\\ \\R,\\ ,3,3,/#)r;request_methodr<r=r-)bytesr rrr strint)r?s"r5r@r@]sJ0 0 0 "'(9":0  3eBis+, ,-0 r4c\V4\\39gQh\V4\JdQVPR9g+VR8Xg$VR8Xd^VPu;8:dR8dMMR #VP^8gQh\ VP R4pV'd VR.8XgQhR #\ VP R4pV'dR\ V^,433#\V4\JdR #R #) HEADCONNECT,content-lengthtransfer-encodingchunkedcontent-length)rPi0)rT)r)chunkedr-)http/1.0r-)typerr status_coderrFrN)rKr<transfer_encodingscontent_lengthss&& r5 _body_framingr^]s ;7H- -- - E{h    +(*,8I8I1OC1O+ +  C'''*%--9MN!j\111'u}}6GHO 3q'9#:"<== E{g''r4c a]tRt^toRt]3V3RlRllt]V3RlRl4t]V3RlRl4t ]V3RlR l4t ]V3R lR l4t V3R lR lt V3RlRlt V3RlRltV3RlRltV3RlRltR0V3RlRllt]V3RlRl4tV3RlRltV3RlRltV3RlR lt]V3R!lR"l4t]V3R#lR$l4t]V3R%lR&l4tV3R'lR(ltV3R)lR*ltV3R+lR,ltV3R-lR.ltR/tVtR#)1r)aAn object encapsulating the state of an HTTP connection. Args: our_role: If you're implementing a client, pass :data:`h11.CLIENT`. If you're implementing a server, pass :data:`h11.SERVER`. max_incomplete_event_size (int): The maximum number of bytes we're willing to buffer of an incomplete event. In practice this mostly sets a limit on the maximum size of the request/response line + headers. If this is exceeded, then :meth:`next_event` will raise :exc:`RemoteProtocolError`. c:<V^8dQhRS[S[,RS[RR/#)r;our_rolemax_incomplete_event_sizer=N)r r&rN)r? __classdict__s"r5r@Connection.__annotate__s-%8%8x.%8$'%8  %8r4cW nV\\39d\RV: 24hWnVV\Jd \VnM \Vn\ 4VnVPVPR\4Vn VPVP R\4Vn \4VnRVnRVnRVnRVnR#)zexpected CLIENT or SERVER, not NF)_max_incomplete_event_sizerr" ValueErrorra their_roler_cstate_get_io_objectr'_writerr_readerr_receive_buffer_receive_buffer_closedtheir_http_version_request_method"client_is_waiting_for_100_continue)selfrarbs&&&r5__init__Connection.__init__s +D' FF+ +>xlKL L  v $DO$DO&( **4==$H **4??D'J  -',#480438/r4cV<V^8dQhRS[S[S[,S[S[,3,/#r;r=)rr r&)r?rcs"r5r@rds&))T(^T(^;<)r4c @\VPP4#)zqA dictionary like:: {CLIENT: , SERVER: } See :ref:`state-machine` for details. )dictristatesrrs&r5ryConnection.statessDLL''((r4c0<V^8dQhRS[S[,/#rvr r&)r?rcs"r5r@rds224>2r4c PVPPVP,#)zZThe current state of whichever role we are playing. See :ref:`state-machine` for details. )riryrarzs&r5 our_stateConnection.our_states ||""4==11r4c0<V^8dQhRS[S[,/#rvr})r?rcs"r5r@rds44T(^4r4c PVPPVP,#)z^The current state of whichever role we are NOT playing. See :ref:`state-machine` for details. )riryrhrzs&r5 their_stateConnection.their_states ||""4??33r4c <V^8dQhRS[/#rv)r>)r?rcs"r5r@rdsUU4Ur4cNVP\J;'d VP#N)rhrrqrzs&r5!they_are_waiting_for_100_continue,Connection.they_are_waiting_for_100_continues&(TTT-T-TTr4c<V^8dQhRR/#r;r=Nr-)r?rcs"r5r@rds33$3r4c \VPP4pVPP4RVnVP 'dQhVP V4R#)aIAttempt to reset our connection state for a new request/response cycle. If both client and server are in :data:`DONE` state, then resets them both to :data:`IDLE` state in preparation for a new request/response cycle on this same connection. Otherwise, raises a :exc:`LocalProtocolError`. See :ref:`keepalive-and-pipelining`. N)rxrirystart_next_cyclerprq_respond_to_state_changes)rr old_statess& r5rConnection.start_next_cyclesR$,,--.  %%'#::::: &&z2r4c4<V^8dQhRS[S[,RR/#)r;roler=Nr})r?rcs"r5r@rds334>3d3r4c\VPP4pVPPV4VP V4R#r)rxriry process_errorr)rrrrs&& r5_process_errorConnection._process_errors6$,,--.  ""4( &&z2r4cF<V^8dQhRS[RS[S[S[,,/#r:)rrr r&)r?rcs"r5r@rds$  % HT(^4L r4c\V4\JdVP^e8Xd\#\V4\JdC\ VP P9d$^VPu;8:dR8d \ #R#R#)erSN)rZrr[rrrripending_switch_proposalsrrr<s&&r5_server_switch_eventConnection._server_switch_eventsc ;/ /E4E4E4L" " ;( "4<<#H#HH5,,2s2&&3r4c:<V^8dQhRS[S[,RS[RR/#)r;rr<r=N)r r&r)r?rcs"r5r@rds&.:.:4>.:%.:D.:r4c\VPP4pV\Jd\ V4\ JdlVP R8Xd VPP\4\VPR4'd VPP\4RpV\JdVPV4pVPPV\ V4V4\ V4\ JdVP VnWP JdW\ V4\ \"\$39d8\'\(\ \"\$3,V4pVP*Vn\ V4\ \"39dK\/\'\(\ \"3,V44'gVPP14\ V4\ Jd\3V4'dRVn\ V4\$\"39dRVnV\Jd"\ V4\6\839dRVnVP;W24R#)rRsupgradeNTF)rxriryrrZrmethodprocess_client_switch_proposalrrrFrr"r process_eventrprhrrrr rDrorIprocess_keep_alive_disabledrrqrrr)rrrr<rserver_switch_events&&& r5_process_eventConnection._process_events$,,--. 6>d5kW4||z) ;;OL z:: ;;OL" 6>"&";";E"B  ""4e6IJ ;' !#(<d5kdL-AA6;D 3 &&z9r4c <V^8dQhRS[S[,RS[S[,RS[S[S[3,RS[S[RS[3,,/#)r;rr<io_dictr=.) r r&rrr rr(rr)r?rcs"r5r@rd@sS..8n..{K/0 . (38$ % .r4c.VPPV,pV\Jd^\\ \ VP 4\ \\\3,V44wrVV\,V,!V!#VPW34#r) riryr!r^rrLrpr rrget)rrrr<rstate framing_typeargss&&&& r5rjConnection._get_io_object@s} ##D) I "/UD0014gx>O8PRW3X" L9%l3T: :;;}- -r4Ncp<V^8dQhRS[S[S[,S[S[,3,RS[S[,RR/#)r;rr<r=N)rr r&rr)r?rcs"r5r@rdVsD P Phh78 P P  Pr4c&VPWP,8wd'VPVPV\4VnVP WP ,8wd)VPVP V\4VnR#R#r) rrarjr'rkrrhrrl)rrrr<s&&&r5r$Connection._respond_to_state_changesVse >>Z 6 6..t}}eWMDL   z//: :..twODL ;r4c6<V^8dQhRS[S[S[3,/#rv)r rLr>)r?rcs"r5r@rdbs JJuUD[1Jr4c D\VP4VP3#)a:Data that has been received, but not yet processed, represented as a tuple with two elements, where the first is a byte-string containing the unprocessed data itself, and the second is a bool that is True if the receive connection was closed. See :ref:`switching-protocols` for discussion of why you'd want this. )rLrmrnrzs&r5 trailing_dataConnection.trailing_dataas d**+T-H-HIIr4c$<V^8dQhRS[RR/#)r;datar=N)rL)r?rcs"r5r@rdls,/,/,/4,/r4c V'd9VP'd \R4hV;PV, unR#RVnR#)aAdd data to our internal receive buffer. This does not actually do any processing on the data, just stores it. To trigger processing, you have to call :meth:`next_event`. Args: data (:term:`bytes-like object`): The new data that was just received. Special case: If *data* is an empty byte-string like ``b""``, then this indicates that the remote side has closed the connection (end of file). Normally this is convenient, because standard Python APIs like :meth:`file.read` or :meth:`socket.recv` use ``b""`` to indicate end-of-file, while other failures to read are indicated using other mechanisms like raising :exc:`TimeoutError`. When using such an API you can just blindly pass through whatever you get from ``read`` to :meth:`receive_data`, and everything will work. But, if you have an API where reading an empty string is a valid non-EOF condition, then you need to be aware of this and make sure to check for such strings and avoid passing them to :meth:`receive_data`. Returns: Nothing, but after calling this you should call :meth:`next_event` to parse the newly received data. Raises: RuntimeError: Raised if you pass an empty *data*, indicating EOF, and then pass a non-empty *data*, indicating more data that somehow arrived after the EOF. (Calling ``receive_data(b"")`` multiple times is fine, and equivalent to calling it once.) z(received close, then received more data?TN)rn RuntimeErrorrm)rrrs&&r5 receive_dataConnection.receive_datals9N ***"#MNN  D ( *.D 'r4cZ<V^8dQhRS[S[S[S[,S[S[,3,/#rvr rr r*r+)r?rcs"r5r@rds) ud9otF|3 4r4cVPpV\JdVP'd\#V\Jg V\ Jd\#VP fQhVP VP4pVffVP'gTVP'dB\VP R4'dVP P4pM \4pVf\pV#)Nread_eof) rrrmr+r r#rlrnhasattrrr r*)rrrr<s& r5_extract_next_receive_event&Connection._extract_next_receive_events   D=T111M ) )U6G-GM||''' T112 ='''D,G,G,G 4<<44 LL113E,.E =E r4cZ<V^8dQhRS[S[S[S[,S[S[,3,/#rvr)r?rcs"r5r@rds(??E%i$v,"FG?r4c BVP\Jd \R4hVP4pV\\ 39d+VP VP\\V44V\JdO\VP4VP8d\RRR7hVP'd \R4hV# \dNpTPTP4\!T\"4'dTP%4Rp?R#hRp?ii;i)anParse the next event out of our receive buffer, update our internal state, and return it. This is a mutating operation -- think of it like calling :func:`next` on an iterator. Returns: : One of three things: 1) An event object -- see :ref:`events`. 2) The special constant :data:`NEED_DATA`, which indicates that you need to read more data from your socket and pass it to :meth:`receive_data` before this method will be able to return any more events. 3) The special constant :data:`PAUSED`, which indicates that we are not in a state where we can process incoming data (usually because the peer has finished their part of the current request/response cycle, and you have not yet called :meth:`start_next_cycle`). See :ref:`flow-control` for details. Raises: RemoteProtocolError: The peer has misbehaved. You should close the connection (possibly after sending some kind of 4xx response). Once this method returns :class:`ConnectionClosed` once, then all subsequent calls will also return :class:`ConnectionClosed`. If this method raises any exception besides :exc:`RemoteProtocolError` then that's a bug -- if it happens please file a bug report! If this method raises any exception then it also sets :attr:`Connection.their_state` to :data:`ERROR` -- see :ref:`error-handling` for discussion. z+Can't receive data when peer state is ERRORzReceive buffer too longi)error_status_hintz#peer unexpectedly closed connectionN)rrr%rr*r+rrhrrlenrmrfrn BaseExceptionr isinstancer$!_reraise_as_remote_protocol_error)rrr<excs& r5 next_eventConnection.next_eventsP   u $%&ST T 446EY//##DOOT%5GH !t++,t/N/NN.1S.....STTL     0#1225577  s%BC9 C DADDDc$<V^8dQhRS[RR/#)r;r<r=N)r )r?rcs"r5r@rds  * t r4cR#rr-rs&&r5sendConnection.send r4cH<V^8dQhRS[S[S[S[S[S[3,RS[/#r:)r rrrrrrL)r?rcs"r5r@rds.  7$98T<WX  r4cR#rr-rs&&r5rrs r4c6<V^8dQhRS[RS[S[,/#r:rrrL)r?rcs"r5r@rds  % HUO r4cR#rr-rs&&r5rrrr4c6<V^8dQhRS[RS[S[,/#r:r)r?rcs"r5r@rds''%'HUO'r4c RVPV4pVfR#RPV4#)aCConvert a high-level event into bytes that can be sent to the peer, while updating our internal state machine. Args: event: The :ref:`event ` to send. Returns: If ``type(event) is ConnectionClosed``, then returns ``None``. Otherwise, returns a :term:`bytes-like object`. Raises: LocalProtocolError: Sending this event at this time would violate our understanding of the HTTP/1.1 protocol. If this method raises any exception then it also sets :attr:`Connection.our_state` to :data:`ERROR` -- see :ref:`error-handling` for discussion. Nr4)send_with_data_passthroughjoin)rrr< data_lists&& r5rrs,*33E:  88I& &r4cF<V^8dQhRS[RS[S[S[,,/#r:)rrrrL)r?rcs"r5r@rd s$(4;:Or4c ~VP\Jd \R4h\V4\JdVP V4pVP pVPVPV4\V4\JdR#VfQh.pV!WP4V# TPTP4h;i)a@Identical to :meth:`send`, except that in situations where :meth:`send` returns a single :term:`bytes-like object`, this instead returns a list of them -- and when sending a :class:`Data` event, this list is guaranteed to contain the exact object you passed in as :attr:`Data.data`. See :ref:`sendfile` for discussion. z'Can't send data when our state is ERRORN) rrr$rZr&_clean_up_response_headers_for_sendingrkrrar appendr)rrr<writerrs&& r5r%Connection.send_with_data_passthrough s >>U "$%NO O E{h&CCEJ \\F    u 5E{..))))+ u../       . sABBB<c<V^8dQhRR/#rr-)r?rcs"r5r@rdAs++T+r4c <VPVP4R#)zNotify the state machine that we failed to send the data it gave us. This causes :attr:`Connection.our_state` to immediately become :data:`ERROR` -- see :ref:`error-handling` for discussion. N)rrarzs&r5 send_failedConnection.send_failedAs DMM*r4c&<V^8dQhRS[RS[/#)r;responser=)r)r?rcs"r5r@rdZs9 9 x9 H9 r4c\V4\JgQhVPpRp\\VP 4pVR8XdRp\ WA4wrVVR 9d\\VR.4pVPeVPR8d"\VR.4pVP R8wdRpM\VRR.4pVPP'd V'dN\\VR44pVPR 4VPR 4\VR\V44p\VVP VP"VP$R 7#) FrQsGETrWrErUTrVrBs keep-aliverC)rFr[rDreason)rXrY)rZrrFrrLrpr^rrori keep_alivesetrdiscardaddsortedr[rDr)rrrrF need_closemethod_for_choosing_headersr_rHs&& r5r1Connection._clean_up_response_headers_for_sendingZs9H~)))"" '+5$2F2F&G# &' 1*0 ''(CN 2 2'w0A2FG&&.$2I2IF2R +74H"M ''72!%J*74H:,W||&&&*-g}EFJ   } - NN8 $&w vj?QRG ,,!..??   r4) rirfrlrmrnrprkrqrarorhr)r/r0r1r2__doc__!DEFAULT_MAX_INCOMPLETE_EVENT_SIZErspropertyryrrrrrrrrjrrrrrr rrrrr3__classdictcell__)rcs@r5r)r)sG $*K%8%8N))22 44 UU33(33  .:.:`.., P PJJ,/,/\8??B      ''6B++29 9 r4N)r)r*r+i@)5typingrrrrrrr r r r _eventsr rrrrrr_headersrrr_readersrr_receivebufferr_staterrrrrrr r!r"r#_utilr$r%r&_writersr'r(__all__r*r+rrIr^r)r-r4r5rs   RQ*)    + 0 H  X %.!0 t| | r4