U hu@sddlZddlZddlZddlZddlZddlZddlZddlZddlZddl Z ddl m Z ddl Z ddl mZmZmZddlmZmZddlmZmZddlmZmZddlmZdd lmZejrd d lm Z ej!ej"gej"fZ#Gd d d Z$GdddZ%dS)N)deque)eventsutilserrors) EventBuilder EventCommon)types functions)GapErrorPrematureEndReason)get_running_loop) __version__)TelegramClientc@seZdZddddZddddZddddZded d d Zd%deed ddZ d&deee dddZ dddddZ ddddZ ddddZddZddddZdddd Zddd!d"Zddd#d$Zd S)' UpdateMethodsrselfcsjzTz:|tjIdH|jIdH}|jdk r4|j|WWStk rPYnXW5|IdHXdSN) disconnectr updatesGetStateRequest disconnected_updates_errorKeyboardInterrupt)rresultr;/tmp/pip-unpacked-wheel-c81u5j2r/telethon/client/updates.py_run_until_disconnected s    z%UpdateMethods._run_until_disconnectedcs$| |_|r |tjIdHdS)z Change the value of `receive_updates`. This is an `async` method, because in order for Telegram to start sending updates again, a request must be made. N)Z _no_updatesr rr)rZreceive_updatesrrrset_receive_updates-sz!UpdateMethods.set_receive_updatescCsR|jr|Sz0z|j|WWStk r>YnXW5|XdS)a Runs the event loop until the library is disconnected. It also notifies Telegram that we want to receive updates as described in https://core.telegram.org/api/updates. If an unexpected error occurs during update handling, the client will disconnect and said error will be raised. Manual disconnections can be made by calling `disconnect() ` or sending a ``KeyboardInterrupt`` (e.g. by pressing ``Ctrl+C`` on the console window running the script). If a disconnection error occurs (i.e. the library fails to reconnect automatically), said error will be raised through here, so you have a chance to ``except`` it on your own code. If the loop is already running, this method returns a coroutine that you should await on your own code. .. note:: If you want to handle ``KeyboardInterrupt`` in your code, simply run the event loop in your code too in any way, such as ``loop.run_forever()`` or ``await client.disconnected`` (e.g. ``loop.run_until_complete(client.disconnected)``). Example .. code-block:: python # Blocks the current task here until a disconnection occurs. # # You will still receive updates, since this prevents the # script from exiting. await client.run_until_disconnected() N)loopZ is_runningrrZrun_until_completerrrrrrun_until_disconnected8s%  z$UpdateMethods.run_until_disconnected)reventcsfdd}|S)a7 Decorator used to `add_event_handler` more conveniently. Arguments event (`_EventBuilder` | `type`): The event builder class or instance to be used, for instance ``events.NewMessage``. Example .. code-block:: python from telethon import TelegramClient, events client = TelegramClient(...) # Here we use client.on @client.on(events.NewMessage) async def handler(event): ... cs||Sr)add_event_handler)fr"rrr decorator|s z#UpdateMethods.on..decoratorr)rr"r&rr%rongszUpdateMethods.onN)rcallbackr"cCsbt|}|dk r0|D]}|j||fqdSt|trB|}n |sNt}|j||fdS)aS Registers a new event handler callback. The callback will be called when the specified event occurs. Arguments callback (`callable`): The callable function accepting one parameter to be used. Note that if you have used `telethon.events.register` in the callback, ``event`` will be ignored, and instead the events you previously registered will be used. event (`_EventBuilder` | `type`, optional): The event builder class or instance to be used, for instance ``events.NewMessage``. If left unspecified, `telethon.events.raw.Raw` (the :tl:`Update` objects with no further processing) will be passed instead. Example .. code-block:: python from telethon import TelegramClient, events client = TelegramClient(...) async def handler(event): ... client.add_event_handler(handler, events.NewMessage) N)rZ _get_handlers_event_buildersappend isinstancetypeRaw)rr(r"Zbuildersrrrr#s$  zUpdateMethods.add_event_handler)rr(r"returncCsjd}|rt|tst|}t|j}|rf|d8}|j|\}}||kr$|rTt||r$|j|=|d7}q$|S)a Inverse operation of `add_event_handler()`. If no event is given, all events for this callback are removed. Returns how many callbacks were removed. Example .. code-block:: python @client.on(events.Raw) @client.on(events.NewMessage) async def handler(event): ... # Removes only the "Raw" handling # "handler" will still receive "events.NewMessage" client.remove_event_handler(handler, events.Raw) # "handler" will stop receiving anything client.remove_event_handler(handler) rr)r+r,lenr))rr(r"foundievcbrrrremove_event_handlers  z"UpdateMethods.remove_event_handlerz5typing.Sequence[typing.Tuple[Callback, EventBuilder]])rr.cCsdd|jDS)a Lists all registered event handlers. Returns A list of pairs consisting of ``(callback, event)``. Example .. code-block:: python @client.on(events.NewMessage(pattern='hello')) async def on_greeting(event): '''Greets someone''' await event.reply('Hi') for callback, event in client.list_event_handlers(): print(id(callback), type(event)) cSsg|]\}}||fqSrr).0r"r(rrr sz5UpdateMethods.list_event_handlers..)r)rrrrlist_event_handlerssz!UpdateMethods.list_event_handlerscs|jtIdHdS)a "Catches up" on the missed updates while the client was offline. You should call this method after registering the event handlers so that the updates it loads can by processed by your script. This can also be used to forcibly fetch new updates if there are any. Example .. code-block:: python await client.catch_up() N)_updates_queueputr ZUpdatesTooLongrrrrcatch_ups zUpdateMethods.catch_upc sjdkpj }d_zhjr4IdHt}r|rjrd | IdHq:|r:j | }j ||j jqdq:tjjkrjtdtjjjfddtjjkrtdjtdtjjj}|r$jtdz|IdH}Wntjtjtj t!fk r}z.jtdt"|jj#WYq:W5d}~XYn2tj$tj%fk r(}zRjtd t"|jj#|r|_&IdHWYqWYq:W5d}~XYntj't(j)fk r}z>jt*d |j#|_&IdHWYqW5d}~XYnVt+k r}z6jtd t"|j|t,-d IdHWYq:W5d}~XYnXj.|j\}}} |rjtd |/0||| q:j1j}|rƈjtd|j2j3z|IdH}Wntj$tj%fk r}zbjt*d|j2j3t"|jj4|t5j6j|r|_&IdHWYqWYq:W5d}~XYntj't(j)fk rd}zNjt*d|j2j3|j4|t5j6j|_&IdHWYqW5d}~XYntj7tj8tjtjtj t!fk r}z>jt*d|j2j3t"|jj4|t5j6jWYq:W5d}~XYntj9tj:fk r jtd|j2j3j4|t5j;jYq:Yn\t+k rz}z<jtd|j2j3t"|j|t,-d IdHWYq:W5d}~XYnXj<||j\}}} |rjtd|j2j3|/0||| q:j=} | t>?} | dkr:zt,@jAB| IdH}Wn,t,jCk r.jtdYq:YnXnq:g} zjD|j| \}} WntEk rlYq:YnX|/0| || q:Wnft,jFk rYnPtGk r}z0jtHdtId|_&IdHW5d}~XYnXdS)NTzAIn-memory entity cache limit reached (%s/%s), flushing to sessioncs|jjkp|jjkSr)_mb_entity_cacheself_id _message_boxmap)idrrr%z,UpdateMethods._update_loop..z\in-memory entities exceed entity_cache_limit after flushing; consider setting a larger limitz9In-memory entity cache at %s/%s after flushing to sessionz&Getting difference for account updatesz9Cannot get difference since Telegram is having issues: %szsz5UpdateMethods._preprocess_updates..)r;rU itertoolschain _entities)rrr_r`entitiesurrrrVs z!UpdateMethods._preprocess_updatesc sdd}|rztj|jddIdHWqWnBtjk rDYn.tjk rZYdStk rpYqYnX|IdH|j sqz|j |Wnt tjfk rYdSX| |j qdS)NcSs tddS)Nll)random randrangerrrrr@rAz/UpdateMethods._keepalive_loop..<)timeout)rCrSrXrrZr[r\Z_clean_exported_sendersZ_senderZ_transport_connectedZ_keepalive_pingConnectionErrorrKsessionsave)rZrndrrr_keepalive_loops.   zUpdateMethods._keepalive_loopc sd}|jjs8z|jddIdHWntk r6YnXt|||}|jD]l}|D]b}|tj}|rr| ||tj }|r| ||tj }|r| ||jrV||IdHqVqN|jD]J\}}|t|} | sq|js||IdH|| } t| r| IdH} | sqz|| IdHWqtjk rht|dt|} |jtd| Yqtjk rt|dt|} |jtd| t| jYqYqtk r } z>t | t!j"r|#rt|dt|} |jt$d| W5d} ~ XYqXqdS)NT)Z input_peerrIEEvent handler "%s" already has an open conversation, ignoring new one=Event handler "%s" stopped chain of propagation for event %s.Unhandled exception on %s)%r;r<get_merREventBuilderDictZ_conversationsvaluesrZ NewMessageZ_on_new_messageZ MessageEditedZ_on_editZ MessageReadZ_on_readZ_customZ _check_customr)r,resolvedresolvefilterinspect isawaitablerAlreadyInConversationErrorgetattrreprrHrIrNStopPropagationr\r+rSr[rCr]) rupdateothersZbuiltZconv_setconvr2builderr(r"r{namer^rrrrD sf              zUpdateMethods._dispatch_updatec sZ|jD]L\}}t|tjrqt||js,q|jsB||IdH||}t |r`|IdH}|sfqz||IdHWqt j k rt |dt |}|jtd|Yqtjk rt |dt |}|jtd|t|jYqVYqtk rR}z>t|tjr |rBt |dt |}|jtd|W5d}~XYqXqdS)zO Dispatches a single, out-of-order event. Used by `AlbumHack`. NrIrsrtru)r)r+rr-Eventryrzr{r|r}rr~rrrHrIrNrr,r\rSr[rCr])rr"rr(r{rr^rrr_dispatch_eventLs@        zUpdateMethods._dispatch_eventc sz|IdHWn:tk rL}z|jtdt||W5d}~XYnXdSz2|jtd|IdH|jtdWnXtj k r}z|jtd|W5d}~XYn$tk r|jt dYnXdS)Nz:Error executing high-level request after reconnect: %s: %sz/Asking for the current state after reconnect...z#Successfully fetched missed updatesz0Failed to get missed updates after reconnect: %rzCUnhandled exception while getting update difference after reconnect) rvr\rHrIrQr,rJr:rZRPCErrorr])rr^rrr_handle_auto_reconnectus,    z$UpdateMethods._handle_auto_reconnect)N)N)rI __module__ __qualname__rrr!rr'Callbackr#intr4r7r:rcrVrrrDrrrrrrrs8  / 4 ' X(C)rc@s&eZdZdZddddZddZdS) rwzI Helper "dictionary" to return events from types and cache them. r)clientcCs||_||_||_dSr)rrr)rrrrrrr__init__szEventBuilderDict.__init__cCsz |j|WStk rz||j|j|jj}|j|<t|trf|j|_ |jj |_ | |jn |rr|j|_ |YSXdSr) __dict__KeyErrorbuildrrrZ_self_idr+rZoriginal_updaterhZ _set_clientZ_client)rrr"rrr __getitem__s   zEventBuilderDict.__getitem__N)rIrr__doc__rrrrrrrwsrw)&rSr|rfrksysrW tracebacktypingloggingrL collectionsrrPrrrZ events.commonrrtlr r Z_updatesr r Zhelpersr versionr TYPE_CHECKINGZtelegramclientrCallableAnyrrrwrrrrs6