vKg'lSSKrSSKrSSKJr "SS5r\"5r"SS5r"SS\5rg) N) exceptionsc*\rSrSrSrSrSrSrSrg)Channelzo The only way for the mitmproxy server to communicate with the master is to use the channel it has been given. c(XlX lX0lgN)masterloop should_exit)selfr r r s l/var/www/highfloat_scraper/venv/lib/python3.13/site-packages/seleniumwire/thirdparty/mitmproxy/controller.py__init__Channel.__init__ s  &cURR5(d[U5Ul[R "UR RRX5UR5 URRR5nU[R:Xa[R"5eU$g)z Decorate a message with a reply attribute, and send it to the master. Then wait for a response. Raises: exceptions.Kill: All connections should be closed immediately. N)r is_setReplyreplyasynciorun_coroutine_threadsafer addonshandle_lifecycler qgetrKill)r mtypemgs r ask Channel.asks&&((AhAG  , , ""33E=   AJOO# oo''H)rcURR5(dT[5Ul[R "UR RRX5UR5 gg)zb Decorate a message with a dummy reply attribute, send it to the master, then return immediately. N) r r DummyReplyrrrr rrr )r rrs r tell Channel.tell$sT &&(( lAG  , , ""33E=  )r)r r r N) __name__ __module__ __qualname____firstlineno____doc__rrr#__static_attributes__rr rrs' & rrcn\rSrSrSrSr\S5r\S5rSr Sr SSjr SS jr SS jr S rS rg )r4z Messages sent through a channel are decorated with a "reply" attribute. This object is used to respond to the message through the return channel. chXl[R"5UlSUl[ UlgNstart)objqueueQueuer_stateNO_REPLYvalue)r r1s r rReply.__init__9s$  rcUR$)ax The state the reply is currently in. A normal reply object goes sequentially through the following lifecycle: 1. start: Initial State. 2. taken: The reply object has been taken to be committed. 3. committed: The reply has been sent back to the requesting party. This attribute is read-only and can only be modified by calling one of state transition functions. )r4r s r state Reply.stateCs{{rc(UR[:g$r)r6r5r9s r has_messageReply.has_messageRszzX%%rcURS:wa/[R"SRUR55eSUlg)z Scripts or other parties make "take" a reply out of a normal flow. For example, intercepted flows are taken out so that the connection thread does not proceed. r0z)Reply is {}, but expected it to be start.takenN)r:rControlExceptionformatr4r9s r take Reply.takeVs> :: --;BB4::N  rc(URS:wa/[R"SRUR55eUR(d[R"S5eSUlUR RUR5 g)z Ultimately, messages are committed. This is done either automatically by the handler if the message is not taken or manually by the entity which called .take(). r@z)Reply is {}, but expected it to be taken.zThere is no reply message. committedN) r:rrArBr=r4rputr6r9s r commit Reply.commitasm :: --;BB4::N --.JK K!   4::rc<URURU5 gr)sendr1r forces r ack Reply.ackps $((E"rcUR[RU5 URS:XaUR 5 gg)Nr@)rKrrr4rHrLs r kill Reply.killss. *//5) ;;' ! KKM "rcURS;a/[R"SRUR55eUR(aU(d[R"S5eXlg)N>r0r@z2Reply is {}, but expected it to be start or taken.z!There is already a reply message.)r:rrArBr=r6)r msgrMs r rK Reply.sendxsX ::/ /--DKKDJJW    E--.QR R rcjURS:wa#[R"SUR-5eg)NrFUncommitted reply: %s)r:rrAr1r9s r __del__ Reply.__del__s. :: $--.E.PQ Q %r)r4r1rr6N)F)r%r&r'r(r)rpropertyr:r=rCrHrNrQrKrXr*r+rr rr4sS  &&  # Rrrc>^\rSrSrSrU4SjrSrSrSrSr U=r $)r"a A reply object that is not connected to anything. In contrast to regular Reply objects, DummyReply objects are reset to "start" at the end of an handler so that they can be used multiple times. Useful when we need an object to seem like it has a channel, and during testing. c2>[TU]S5 SUlg)NF)superr _should_reset)r __class__s r rDummyReply.__init__s "rcxURS:wa#[R"SUR-5eSUlg)NrFrWT)r:rrAr1r_r9s r mark_resetDummyReply.mark_resets1 :: $--.E.PQ Q!rcLUR(aSUl[Ulggr/)r_r4r5r6r9s r resetDummyReply.resets   !DK!DJ rcgrr+r9s r rXDummyReply.__del__s r)r_r4r6) r%r&r'r(r)rrcrfrXr* __classcell__)r`s@r r"r"s! #" "   rr") rr2!seleniumwire.thirdparty.mitmproxyrrobjectr5rr"r+rr rms= 8''T 8PRPRf  r