+ kHj~Rt^RIt^RIt^RIt^RIHt^RIHt^RIH t ]P!R4t !RR4t R#)zTelegram held-inbound queue: events PTB already acked that cannot dispatch yet are held, redispatched on reconnect, and handed to the adapter that replaces this one (#132829).N)Optional) MessageEvent) cancel_taskz"plugins.platforms.telegram.adapterca]tRt^toRtV3RlRltRR/V3RlRlltV3RlR ltV3R lR ltV3R lR lt RV3RlRllt Rt Vt R#)TelegramHeldInboundMixinzHHold / redispatch / hand-over of inbound events for ``TelegramAdapter``.c<V^8dQhRR/#)returnN)format __classdict__s"U/home/ubuntu/.hermes/hermes-agent/plugins/platforms/telegram/telegram_held_inbound.py __annotate__%TelegramHeldInboundMixin.__annotate__sHH4Hc VP4'gVP4'dR#\VRR4'gR#\P!4p\TRR4p\P !4pTeTP4'gY#JdR#TPTPY#JdRMTR74Tn R# \ dR#i;i \ dRpLqi;i)zEnsure a tracked drain runs when held events exist and delivery is live (no-op while down or after permanent fatal; an in-flight drain schedules its own follow-up).N_held_inbound_events_held_inbound_redispatch_task)prior) _is_permanent_fatal_should_drop_delayed_deliverygetattrasyncioget_running_loop RuntimeError current_taskdone create_task_redispatch_held_inboundr)selflooprcurrents& r !_schedule_held_inbound_redispatch:TelegramHeldInboundMixin._schedule_held_inbound_redispatchs  # # % %)K)K)M)M t3T::  ++-D=tD **,G  UZZ\\e6J -1-=-=d>[>[jojzbfAF>[?G.H*     G s$C (C CC C/.C/scheduleTc0<V^8dQhRS[RS[RS[RR/#reventwherer$r Nrstrbool)r r s"r rr&s+#5#5#5#5PT#5`d#5rc  BaVP4'd8\PRT\\ SRR4;'gR44R#\ VRR4pVeV!4MRpVe*VP 4VP SV R2VR7R#\ VRR4pVf .;Vnp\;QJdV3R lV4F 'gK R M R M!V3R lV44'dR#\\ VR ^@4;'g^@4p\V4V8dIVP^4p\PR T\\ VRR4;'gR44KXVPS4VP 4\PRT\\ SRR4;'gR4\V4VP4'dRM V'dRMR4V'd+VP4'gVP4R#R#R#)uPreserve an inbound event that cannot be dispatched now (PTB already acked the update, so dropping is silent loss). Capped, identity-deduped; permanent fatal discards. ``schedule=False`` inside a drain avoids poison-event loops. The disconnect drop-guard (#55971) correctly prevents dispatch into a torn-down session. Destroying the event is wrong: by the time we reach enqueue/flush, python-telegram-bot has already acked the update and advanced the offset — silent permanent loss, no log, no error. zF[Telegram] Discarding inbound under non-retryable fatal (%s, %d chars)textN_held_inbound_successorz -forwardedr(r$rc3*<"TFqSJxK R#5iNr ).0existingr's& r ?TelegramHeldInboundMixin._hold_inbound_event..;s6X5 sTFHELD_INBOUND_MAXzC[Telegram] Held-inbound queue full (%d); dropping oldest (%d chars)z5[Telegram] Holding inbound (%s, %d chars, queue=%d)%sz - will redispatch on reconnectz - scheduling redispatch)rloggerwarninglenr_accept_update_adopt_held_eventranyintpopappendrr") rr'r(r$ successortargetheldmax_ndroppeds &f$$ r _hold_inbound_event,TelegramHeldInboundMixin._hold_inbound_event&s  # # % % NNXZ_adelmrtz}AfBfHfHFHbI J D";TB ) 54      !  $ $UUG:2FQY $ Z t3T: >@@  2 2 4A8rc"<V^8dQhRRRR/#)r predecessorrr Nr )r r s"r rrKs 1 1.H 1T 1rc RVn\P!V4Vn\VRR4;'g.p\ V4pVP 4VFpVP VRRR7K VP4R#)zTake over the hold queue of the instance the runner just replaced with us (#132829): it only drains on its own ``_mark_connected``, which never comes; later holds there forward here.NradoptedFr0)r/weakrefrefrlistclearr<r")rrIrCeventsr's&& r adopt_held_inbound+TelegramHeldInboundMixin.adopt_held_inboundKsq(,$.5kk$.? +{$:DAGGRd E  " "5 E " J ..0rc0<V^8dQhRS[RS[RS[RR/#r&r))r r s"r rrWs0HH|HsHdHW[Hrc \VRR4e&\P!V4VPnVP WVR7R#)z_Hold a predecessor's event here; only the transport ref moves (profile/authz stay as resolved).sourceNr0)rrLrMrU_transport_adapter_refrF)rr'r(r$s&&$$r r<*TelegramHeldInboundMixin._adopt_held_eventWs9 5(D ) 529++d2CELL /   h Grc0<V^8dQhRS[RS[RS[RR/#)rrPidxr(r N)rNr>r*)r r s"r rr]s/HH4HcH#H$Hrc BWRFpVPWCRR7K R#)zWRe-hold ``events[idx:]`` without rescheduling (drain interrupted / failed / cancelled).NFr0)rF)rrPrYr(rests&&&& r _rehold_from%TelegramHeldInboundMixin._rehold_from]s#4LD  $ $T $ G!rNcH<V^8dQhRS[S[P,RR/#)rrr N)rrTask)r r s"r rrbs%,9,9HW\\4J,9VZ,9rc "V\P!4Jd\V4GRjxL \VRR4pVP 4'd<V'd2\ V4pVP 4\PRV4R#V'gR#\V4pVP 4\PR\ V44Rp\V4FwrgVP 4'gVP4'duVPWFR4V'dX\VRR4'dCVP4'g+VP 4'gVP4R#R#R#R#R#VPV4GRjxL K V'dX\VRR4'dCVP4'g+VP 4'gVP4R#R#R#R#R#ELLl \PdTPYFR4h\ d\P#R\ \TR R4;'gR 44TPYFR 4R pT'dX\TRR4'dCTP4'g+TP 4'gTP4R#R#R#R#R#i;i T'dT\TRR4'd@TP4'g)TP 4'gTP4iiiii;i5i) zDrain the hold queue after reconnect or a connected-path hold; ``prior`` (previous redispatch task) is cancelled+awaited here so ``_mark_connected`` stays synchronous.NrzR[Telegram] Redispatch aborted; discarded %d held inbound under non-retryable fatalz3[Telegram] Redispatching %d held inbound message(s)Tzredispatch-interruptedzredispatch-cancelledzC[Telegram] Failed to redispatch held inbound (%d chars); re-holdingr-r.zredispatch-failedF)rrrrrr:rOr8r9rN enumeraterr\r"handle_messageCancelledError Exception exception)rrrCnrPallow_followup_schedulerYr's&& r r1TelegramHeldInboundMixin._redispatch_held_inboundbs ,,. .e$ $ $t3T:  # # % %I suvw  d LcRXkZ"& 9'/ ++--1S1S1U1U%%f3KL"(D"8$??::<<00226683=@(! --e444 0((D"8$??::<<00226683=@(I %*5--%%f3IJ $$]_bcjkprxz~cdFdFDF`GH%%f3FG.3+(D"8$??::<<00226683=@((D"8$??::<<00226683=@(s(M H.M :M >M ;K)K)#0M M *M HHHK)"0M M )M H0K&9)K&#K&K)0M 5M  M %K&&K))1MM1MM )rrr/r2) __name__ __module__ __qualname____firstlineno____doc__r"rFrQr<r\r__static_attributes____classdictcell__)r s@r rrsXRHH(#5W[#5#5J 1 1HH HH ,9,9,9rr) rmrloggingrLtypingrgateway.platforms.eventrgateway.platforms.helpersr getLoggerr8rr rr rus<Z01   ? @99r