vjQ&ddlmZddlZddlZddlZddlmZmZddlm Z ddl m Z m Z m Z mZddlmZdgZej"d ZGd dZy) ) annotationsN)Iteratorcast)ConcurrencyError) OP_BINARYOP_CONTOP_TEXTFrame)Data Assemblerzutf-8c:eZdZdZddZd d dZd dZd dZddZy) r z) Assemble messages from frames. ctj|_tj|_tj|_d|_d|_d|_g|_ d|_ d|_ y)NF) threadingLockmutexEventmessage_completemessage_fetchedget_in_progressput_in_progressdecoderchunks chunks_queueclosedselfs i/workspace/moltex-experiments/.pixi/envs/default/lib/python3.12/site-packages/websockets/sync/messages.py__init__zAssembler.__init__sk^^% !* 1(0 %$:> #% DH Nc|j5|jr td|jr t dd|_ddd|j j |}|j5d|_|std|dd|jr td|j jsJ|j j|jd nd }|j|j}g|_ |jJ|jjrJ|jj|cdddS#1swYxYw#1swYyxYw) a# Read the next message. :meth:`get` returns a single :class:`str` or :class:`bytes`. If the message is fragmented, :meth:`get` waits until the last frame is received, then it reassembles the message and returns it. To receive messages frame by frame, use :meth:`get_iter` instead. Args: timeout: If a timeout is provided and elapses before a complete message is received, :meth:`get` raises :exc:`TimeoutError`. Raises: EOFError: If the stream of frames has ended. ConcurrencyError: If two threads run :meth:`get` or :meth:`get_iter` concurrently. TimeoutError: If a timeout is provided and elapses before a complete message is received. stream of frames ended&get() or get_iter() is already runningTNFz timed out in z.1fsr )rrEOFErrorrrrwait TimeoutErroris_setclearrjoinrrrset)rtimeout completedjoinermessages rgetz Assembler.get>s@,ZZ{{788##&'OPP#'D ))..w7 ZZ#(D "]73-q#ABB{{788((//1 11  ! ! ' ' )"&,,"63BF"KK 4GDK$$, ,,++224 44  $ $ &1ZZZs6E2CE'E$'E0c#K|j5|jr td|jr t d|j }g|_t dtj|_ |jjr|jjdd|_dddD]}||jjx}!||jjx}!|j5d|_|jr td|jjsJ|jj|j gk(sJd|_ |jjrJ|jj!dddy#1swY xYw#1swYyxYww)a~ Stream the next message. Iterating the return value of :meth:`get_iter` yields a :class:`str` or :class:`bytes` for each frame in the message. The iterator must be fully consumed before calling :meth:`get_iter` or :meth:`get` again. Else, :exc:`ConcurrencyError` is raised. This method only makes sense for fragmented messages. If messages aren't fragmented, use :meth:`get` instead. Raises: EOFError: If the stream of frames has ended. ConcurrencyError: If two threads run :meth:`get` or :meth:`get_iter` concurrently. r"r#zqueue.SimpleQueue[Data | None]NTF)rrr&rrrrqueue SimpleQueuerrr)putr1r*rr,)rrchunks rget_iterzAssembler.get_iter|s&ZZ{{788##&'OPP[[FDK $0!!#!D $$++-!!%%d+#'D +2EK))--//u<K))--//u<ZZ#(D {{788((//1 11  ! ! ' ' );;"$ $$ $D ++224 44  $ $ &Z=Z<Zs= GB!F80AG G B#G/ G8G=GG Gc|j5|jr td|jr t d|j t urtd|_n.|j turd|_n|j tusJ|j1|jj|j|j}n |j}|j|jj!|n|jj#||js dddy|j$j'rJ|j$j)|j|jj#d|j*j'rJd|_ddd|j*j-|j5d|_|jr td|j*j'sJ|j*j/d|_dddy#1swYxYw#1swYyxYw)a, Add ``frame`` to the next message. When ``frame`` is the final frame in a message, :meth:`put` waits until the message is fetched, which can be achieved by calling :meth:`get` or by fully consuming the return value of :meth:`get_iter`. :meth:`put` assumes that the stream of frames respects the protocol. If it doesn't, the behavior is undefined. Raises: EOFError: If the stream of frames has ended. ConcurrencyError: If two threads run :meth:`put` concurrently. r"zput is already runningstrict)errorsNTF)rrr&rropcoder UTF8Decoderrrr decodedatafinrrappendr5rr)r,rr'r*)rframer>s rr5z Assembler.puts ZZ{{788##&'?@@||w&*(; *# ||w...||'||**5::uyyAzz  ( ""4(!!%%d+995Z<,,335 55  ! ! % % '  ,!!%%d+++224 44#'D MT !!# ZZ#(D {{788''..0 00  & & (DLZYZXZs DI0BIAII Icf|j5|jr dddyd|_|jrA|jj |j |j j d|jr|jj dddy#1swYyxYw)z End the stream of frames. Callling :meth:`close` concurrently with :meth:`get`, :meth:`get_iter`, or :meth:`put` is safe. They will raise :exc:`EOFError`. NT) rrrrr,rr5rrrs rclosezAssembler.closesZZ{{ZDK##%%))+$$0%%))$/##$$((*ZZsB'A:B''B0)returnNone)N)r-z float | NonerDr )rDzIterator[Data])rAr rDrE) __name__ __module__ __qualname____doc__rr1r7r5rCr rr r s% $L<|?'BF P+r ) __future__rcodecsr3rtypingrr exceptionsrframesrr r r r __all__getincrementaldecoderr<r rJr rrRsG" !)77 -*f**73 I+I+r