o

;j-��@sX
dZd
dl
Z
d
dlZd
dlZd
dlZd
dlZd
dlZd
dlZd
dl	Z	d
dl
Z
d
dlZd
dlZd
dl
mZ
d
dlmZmZmZmZmZ
d
dlmZ
d
dlmZmZmZ
d
dlZd
dlmZmZmZmZm Z m!Z!m"Z"m#Z#
ej$r�d
dlm%Z%m&Z&m'Z'm(Z(
d
d	l)m*Z*
ne+Z*Gd
d�de*�Z,e!d�
Z-e!d
e,d�Z.Gdd�de�Z/Gdd�d�Z0Gdd�d�Z1dS)a�
An I/O event loop for non-blocking sockets.

In Tornado 6.0, `.IOLoop` is a wrapper around the `asyncio` event loop, with a
slightly different interface. The `.IOLoop` interface is now provided primarily
for backwards compatibility; new code should generally use the `asyncio` event
loop interface directly. The `IOLoop.current` class method provides the
`IOLoop` instance corresponding to the running `asyncio` event loop.

�N)
�isawaitable)�Future�	is_future�chain_future�future_set_exc_info�future_add_done_callback)
�app_log)�Configurable�TimeoutError�
import_object)�Union�Any�Type�Optional�Callable�TypeVar�Tuple�	Awaitable)�Dict�List�Set�	TypedDict)
�Protocolc@s$eZ
dZd
efdd�Zddd�ZdS)�_Selectable�returnc


C�dS�
N��
�selfrr�B/opt/saltstack/salt/lib/python3.10/site-packages/tornado/ioloop.py�fileno=�
z_Selectable.filenoNc


Crrrrrrr �close@r"z_Selectable.close�rN)�__name__�
__module__�__qualname__�intr!r#rrrr r<s
r�_T�_S)
�boundc
seZ
dZd
ZdZdZdZdZe�Z	e
�Zeddde
d	d
f�f
dd��
Zedod
d��
Zdpdd�Zedpdd��
Zejedodd��
�
Zejedqded	edfdd��
�
Zedqded	edfdd��
Zdpdd�Zdpdd�Zedpdd��
Zedpdd ��
Zdpd!d"�Zed	eefd#d$��
Zed	eefd%d&��
Z dqd'ed	d
fd(d)�Z!drd+ed	d
fd,d-�Z"ejd.e#d/e$e#e#gd
fd0e#d	d
fd1d2��
Z%ejd.e&d/e$e&e#gd
fd0e#d	d
fd3d2��
Z%d.e'e#e(fd/e$d4d0e#d	d
fd5d2�Z%d.e'e#e(fd0e#d	d
fd6d7�Z)d.e'e#e(fd	d
fd8d9�Z*dpd:d;�Z+dpd<d=�Z,dsd>e$d?ee-d	e
fd@dA�Z.d	e-fdBdC�Z/dDe'e-e0j1fdEe$dFe
de
d	e2f
dGdH�Z3dIe-dEe$dFe
de
d	e2f
dJdK�Z4dLe-dEe$dFe
de
d	e2f
dMdN�Z5d?e2d	d
fdOdP�Z6dEe$dFe
de
d	d
fdQdR�Z7dEe$dFe
de
d	d
fdSdT�Z8dEe$dFe
de
d	d
fdUdV�Z9dWdXdEe$dYg
d
fd	d
fdZd[�Z:d\ee;j<j=d>e$d]e>fdFe
d	dYfd^d_�Z?d\e;j<j=d	d
fd`da�Z@dEe$ge
fd	d
fdbdc�ZAdWeBd	d
fddde�ZCd.e'e#e(fd	eDe#e'e#e(fffdfdg�ZEd.e'e#e(fd	d
fdhdi�ZFdjeBd	d
fdkdl�ZGdjeBd	d
fdmdn�ZH�ZIS)t�IOLoopa�An I/O event loop.

    As of Tornado 6.0, `IOLoop` is a wrapper around the `asyncio` event loop.

    Example usage for a simple TCP server:

    .. testcode::

        import asyncio
        import errno
        import functools
        import socket

        import tornado
        from tornado.iostream import IOStream

        async def handle_connection(connection, address):
            stream = IOStream(connection)
            message = await stream.read_until_close()
            print("message from client:", message.decode().strip())

        def connection_ready(sock, fd, events):
            while True:
                try:
                    connection, address = sock.accept()
                except BlockingIOError:
                    return
                connection.setblocking(0)
                io_loop = tornado.ioloop.IOLoop.current()
                io_loop.spawn_callback(handle_connection, connection, address)

        async def main():
            sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM, 0)
            sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
            sock.setblocking(0)
            sock.bind(("", 8888))
            sock.listen(128)

            io_loop = tornado.ioloop.IOLoop.current()
            callback = functools.partial(connection_ready, sock)
            io_loop.add_handler(sock.fileno(), callback, io_loop.READ)
            await asyncio.Event().wait()

        if __name__ == "__main__":
            asyncio.run(main())

    Most applications should not attempt to construct an `IOLoop` directly,
    and instead initialize the `asyncio` event loop and use `IOLoop.current()`.
    In some cases, such as in test frameworks when initializing an `IOLoop`
    to be run in a secondary thread, it may be appropriate to construct
    an `IOLoop` with ``IOLoop(make_current=False)``.

    In general, an `IOLoop` cannot survive a fork or be shared across processes
    in any way. When multiple processes are being used, each process should
    create its own `IOLoop`, which also implies that any objects which depend on
    the `IOLoop` (such as `.AsyncHTTPClient`) must also be created in the child
    processes. As a guideline, anything that starts processes (including the
    `tornado.process` and `multiprocessing` modules) should do so as early as
    possible, ideally the first thing the application does after loading its
    configuration, and *before* any calls to `.IOLoop.start` or `asyncio.run`.

    .. versionchanged:: 4.2
       Added the ``make_current`` keyword argument to the `IOLoop`
       constructor.

    .. versionchanged:: 5.0

       Uses the `asyncio` event loop by default. The ``IOLoop.configure`` method
       cannot be used on Python 3 except to redundantly specify the `asyncio`
       event loop.

    .. versionchanged:: 6.3
       ``make_current=True`` is now the default when creating an IOLoop -
       previously the default was to make the event loop current if there wasn't
       already a current one.
    r
�
���implz$Union[None, str, Type[Configurable]]�kwargsrNcsRd
dlm
}
t|
t�rt|
�
}
t|
t�rt|
|�std�
�
t�j	|
f
i|�
�

dS)Nr
)
�BaseAsyncIOLoopz5only AsyncIOLoop is allowed when asyncio is available)
�tornado.platform.asyncior2�
isinstance�strr�type�
issubclass�RuntimeError�super�	configure)�clsr0r1r2�
�	__class__rr r:�s




zIOLoop.configurecCst�
�S)
aKDeprecated alias for `IOLoop.current()`.

        .. versionchanged:: 5.0

           Previously, this method returned a global singleton
           `IOLoop`, in contrast with the per-thread `IOLoop` returned
           by `current()`. In nearly all cases the two were the same
           (when they differed, it was generally used from non-Tornado
           threads to communicate back to the main thread's `IOLoop`).
           This distinction is not present in `asyncio`, so in order
           to facilitate integration with that package `instance()`
           was changed to be an alias to `current()`. Applications
           using the cross-thread communications aspect of
           `instance()` should instead set their own global variable
           to point to the `IOLoop` they want to use.

        .. deprecated:: 5.0
        )r,�currentrrrr �instance�szIOLoop.instancec

Cs|��
d
S)a`
Deprecated alias for `make_current()`.

        .. versionchanged:: 5.0

           Previously, this method would set this `IOLoop` as the
           global singleton used by `IOLoop.instance()`. Now that
           `instance()` is an alias for `current()`, `install()`
           is an alias for `make_current()`.

        .. deprecated:: 5.0
        N)
�make_currentrrrr �install�szIOLoop.installcCst�
�
d
S)ak
Deprecated alias for `clear_current()`.

        .. versionchanged:: 5.0

           Previously, this method would clear the `IOLoop` used as
           the global singleton by `IOLoop.instance()`. Now that
           `instance()` is an alias for `current()`,
           `clear_instance()` is an alias for `clear_current()`.

        .. deprecated:: 5.0

        N)r,�
clear_currentrrrr �clear_instance�szIOLoop.clear_instancec
Crrrrrrr r>��zIOLoop.currentTr?c


Crrr�
r?rrr r>�rDc
Cs~zt�
�}
Wnty


|sYd
St��}
t�|
�

Yn
wztj|
WSty>


|r9ddlm	}
|�}Y|Sd
}Y|Sw)aCReturns the current thread's `IOLoop`.

        If an `IOLoop` is currently running or has been marked as
        current by `make_current`, returns that instance.  If there is
        no current `IOLoop` and ``instance`` is true, creates one.

        .. versionchanged:: 4.1
           Added ``instance`` argument to control the fallback to
           `IOLoop.instance()`.
        .. versionchanged:: 5.0
           On Python 3, control of the current `IOLoop` is delegated
           to `asyncio`, with this and other methods as pass-through accessors.
           The ``instance`` argument now controls whether an `IOLoop`
           is created automatically when there is none, instead of
           whether we fall back to `IOLoop.instance()` (which is now
           an alias for this method). ``instance=False`` is deprecated,
           since even if we do not create an `IOLoop`, this method
           may initialize the asyncio loop.

        .. deprecated:: 6.2
           It is deprecated to call ``IOLoop.current()`` when no `asyncio`
           event loop is running.
        Nr
)
�AsyncIOMainLoop)
�asyncioZget_event_loopr8Znew_event_loopZset_event_loopr,�_ioloop_for_asyncio�KeyErrorr3rF)r?ZlooprFr>rrr r>�s$




�



�
�c

Cstj
d
tdd�
|��
dS)a�Makes this the `IOLoop` for the current thread.

        An `IOLoop` automatically becomes current for its thread
        when it is started, but it is sometimes useful to call
        `make_current` explicitly before starting the `IOLoop`,
        so that code run at startup time can find the right
        instance.

        .. versionchanged:: 4.1
           An `IOLoop` created while there is no current `IOLoop`
           will automatically become current.

        .. versionchanged:: 5.0
           This method also sets the current `asyncio` event loop.

        .. deprecated:: 6.2
           Setting and clearing the current event loop through Tornado is
           deprecated. Use ``asyncio.set_event_loop`` instead if you need this.
        z6make_current is deprecated; start the event loop first��
�
stacklevelN)�warnings�warn�DeprecationWarning�
_make_currentrrrr r@"
s


�zIOLoop.make_currentc


C�t��
r�
�NotImplementedErrorrrrr rP=
szIOLoop._make_currentcCstj
d
tdd�
t��
dS)z�Clears the `IOLoop` for the current thread.

        Intended primarily for use by test frameworks in between tests.

        .. versionchanged:: 5.0
           This method also clears the current `asyncio` event loop.
        .. deprecated:: 6.2
        zclear_current is deprecatedrJrKN)rMrNrOr,�_clear_currentrrrr rBA
s



�zIOLoop.clear_currentc
Cs$tj
d
d�
}|du
r|��
dSdS)NFrE)r,r>�_clear_current_hook)
�oldrrr rTR
s

�zIOLoop._clear_currentc


Csd
S)z�Instance method called when an IOLoop ceases to be current.

        May be overridden by subclasses as a counterpart to make_current.
        Nrrrrr rUX
szIOLoop._clear_current_hookc


CstSr)
r,)
r;rrr �configurable_base_
szIOLoop.configurable_basec
Csd
dlm
}

|
S)Nr
)
�AsyncIOLoop)r3rX)r;rXrrr �configurable_defaultc
szIOLoop.configurable_defaultr@cCs|
r|��
dSdSr)
rP)rr@rrr �
initializei
s

�zIOLoop.initializeF�all_fdsc
CrQ)
a�Closes the `IOLoop`, freeing any resources used.

        If ``all_fds`` is true, all file descriptors registered on the
        IOLoop will be closed (not just the ones created by the
        `IOLoop` itself).

        Many applications will only use a single `IOLoop` that runs for the
        entire lifetime of the process.  In that case closing the `IOLoop`
        is not necessary since everything will be cleaned up when the
        process exits.  `IOLoop.close` is provided mainly for scenarios
        such as unit tests, which create and destroy a large number of
        ``IOLoops``.

        An `IOLoop` must be completely stopped before it can be closed.  This
        means that `IOLoop.stop()` must be called *and* `IOLoop.start()` must
        be allowed to return before attempting to call `IOLoop.close()`.
        Therefore the call to `close` will usually appear just after
        the call to `start` rather than near the call to `stop`.

        .. versionchanged:: 3.1
           If the `IOLoop` implementation supports non-integer objects
           for "file descriptors", those objects will have their
           ``close`` method when ``all_fds`` is true.
        rR)rr[rrr r#m
szIOLoop.close�fd�handler�eventsc
Crrr�rr\r]r^rrr �add_handler�
�zIOLoop.add_handlerc
Crrrr_rrr r`�
ra).Nc
CrQ)
a+Registers the given handler to receive the given events for ``fd``.

        The ``fd`` argument may either be an integer file descriptor or
        a file-like object with a ``fileno()`` and ``close()`` method.

        The ``events`` argument is a bitwise or of the constants
        ``IOLoop.READ``, ``IOLoop.WRITE``, and ``IOLoop.ERROR``.

        When an event occurs, ``handler(fd, events)`` will be run.

        .. versionchanged:: 4.0
           Added the ability to pass file-like objects in addition to
           raw file descriptors.
        rRr_rrr r`�
sc
CrQ)
z�Changes the events we listen for ``fd``.

        .. versionchanged:: 4.0
           Added the ability to pass file-like objects in addition to
           raw file descriptors.
        rR)rr\r^rrr �update_handler�
�zIOLoop.update_handlerc
CrQ)
z�Stop listening for events on ``fd``.

        .. versionchanged:: 4.0
           Added the ability to pass file-like objects in addition to
           raw file descriptors.
        rR�rr\rrr �remove_handler�
rczIOLoop.remove_handlerc


CrQ)
z�Starts the I/O loop.

        The loop will run until one of the callbacks calls `stop()`, which
        will make the loop stop after the current event iteration completes.
        rRrrrr �start�
szIOLoop.startc


CrQ)
a�
Stop the I/O loop.

        If the event loop is not currently running, the next call to `start()`
        will return immediately.

        Note that even after `stop` has been called, the `IOLoop` is not
        completely stopped until `IOLoop.start` has also returned.
        Some work that was scheduled before the call to `stop` may still
        be run before the `IOLoop` shuts down.
        rRrrrr �stop�
szIOLoop.stop�func�timeoutcs�tj
r
td
tttd��}ddd��
d��
�fdd�}��|�

|du
r6d�
�fdd	�}�����||�}��	�
|du
rC��
|�

�
d
du
sKJ�
�
d
��sW�
d
��se�
drat
d|�
�
td
�
�
�
d
��S)a�Starts the `IOLoop`, runs the given function, and stops the loop.

        The function must return either an awaitable object or
        ``None``. If the function returns an awaitable object, the
        `IOLoop` will run until the awaitable is resolved (and
        `run_sync()` will return the awaitable's result). If it raises
        an exception, the `IOLoop` will stop and the exception will be
        re-raised to the caller.

        The keyword-only argument ``timeout`` may be used to set
        a maximum duration for the function.  If the timeout expires,
        a `asyncio.TimeoutError` is raised.

        This method is useful to allow asynchronous calls in a
        ``main()`` function::

            async def main():
                # do stuff...

            if __name__ == '__main__':
                IOLoop.current().run_sync(main)

        .. versionchanged:: 4.3
           Returning a non-``None``, non-awaitable value is now an error.

        .. versionchanged:: 5.0
           If a timeout occurs, the ``func`` coroutine will be cancelled.

        .. versionchanged:: 6.2
           ``tornado.util.TimeoutError`` is now an alias to ``asyncio.TimeoutError``.
        �
FutureCell)�future�timeout_calledNFrcs�z��}|du
rd
dlm
}

|
|�
}Wnty*


t�}|�
d<t|t���
Ynwt|�
r4|�
d<nt�}|�
d<|�|�

�
ddu
sHJ�
��	�
d�f
dd��
dS)Nr
)
�convert_yieldedrkc

s���Sr)
rg)
rkrrr �<lambda>sz.IOLoop.run_sync.<locals>.run.<locals>.<lambda>)
Ztornado.genrm�	Exceptionrr�sys�exc_inforZ
set_result�
add_future)�resultrmZfut�rh�future_cellrrr �run�
s$



�



�






zIOLoop.run_sync.<locals>.runcs4d
�d<�ddu
sJ�
�d��s�
�
�
dSdS)NTrlrk)�cancelrgr)rurrr �timeout_callbacks


�z)IOLoop.run_sync.<locals>.timeout_callbackrkrlz$Operation timed out after %s secondsz+Event loop stopped before Future completed.r$)�typing�
TYPE_CHECKINGrrr�bool�add_callback�add_timeout�timerf�remove_timeoutZ	cancelledZdoner
r8rs)rrhrirjrvrxZtimeout_handlerrtr �run_sync�
s& 

�











zIOLoop.run_syncc

Cst��S)
a�
Returns the current time according to the `IOLoop`'s clock.

        The return value is a floating-point number relative to an
        unspecified time in the past.

        Historically, the IOLoop could be customized to use e.g.
        `time.monotonic` instead of `time.time`, but this is not
        currently supported and so this method is equivalent to
        `time.time`.

        )
r~rrrr r~%szIOLoop.time�deadline�callback�argscOsdt|
t
j�r|j|
|g|�
Ri|�
�
St|
tj�r,|j|��|
��|g|�
Ri|�
�
Std
|
�
�
)a�Runs the ``callback`` at the time ``deadline`` from the I/O loop.

        Returns an opaque handle that may be passed to
        `remove_timeout` to cancel.

        ``deadline`` may be a number denoting a time (on the same
        scale as `IOLoop.time`, normally `time.time`), or a
        `datetime.timedelta` object for a deadline relative to the
        current time.  Since Tornado 4.0, `call_later` is a more
        convenient alternative for the relative case since it does not
        require a timedelta object.

        Note that it is not safe to call `add_timeout` from other threads.
        Instead, you must use `add_callback` to transfer control to the
        `IOLoop`'s thread, and then call `add_timeout` from there.

        Subclasses of IOLoop must implement either `add_timeout` or
        `call_at`; the default implementations of each will call
        the other.  `call_at` is usually easier to implement, but
        subclasses that wish to maintain compatibility with Tornado
        versions prior to 4.0 must use `add_timeout` instead.

        .. versionchanged:: 4.0
           Now passes through ``*args`` and ``**kwargs`` to the callback.
        �Unsupported deadline %r)	r4�numbers�Real�call_at�datetime�	timedeltar~�
total_seconds�	TypeError)rr�r�r�r1rrr r}3s 



�
�
�zIOLoop.add_timeout�delaycOs"|j|�
�|
|g|�
Ri|�
�
S)
a�
Runs the ``callback`` after ``delay`` seconds have passed.

        Returns an opaque handle that may be passed to `remove_timeout`
        to cancel.  Note that unlike the `asyncio` method of the same
        name, the returned object does not have a ``cancel()`` method.

        See `add_timeout` for comments on thread-safety and subclassing.

        .. versionadded:: 4.0
        )r�r~)rr�r�r�r1rrr �
call_later\s"
zIOLoop.call_later�whencOs|j|
|g|�
Ri|�
�
S)
a�
Runs the ``callback`` at the absolute time designated by ``when``.

        ``when`` must be a number using the same reference point as
        `IOLoop.time`.

        Returns an opaque handle that may be passed to `remove_timeout`
        to cancel.  Note that unlike the `asyncio` method of the same
        name, the returned object does not have a ``cancel()`` method.

        See `add_timeout` for comments on thread-safety and subclassing.

        .. versionadded:: 4.0
        )
r})rr�r�r�r1rrr r�kszIOLoop.call_atc
CrQ)
z�Cancels a pending timeout.

        The argument is a handle as returned by `add_timeout`.  It is
        safe to call `remove_timeout` even if the callback has already
        been run.
        rR)rrirrr r}rczIOLoop.remove_timeoutc
OrQ)
a�
Calls the given callback on the next I/O loop iteration.

        It is safe to call this method from any thread at any time,
        except from a signal handler.  Note that this is the **only**
        method in `IOLoop` that makes this thread-safety guarantee; all
        other interaction with the `IOLoop` must be done from that
        `IOLoop`'s thread.  `add_callback()` may be used to transfer
        control from other threads to the `IOLoop`'s thread.
        rR�rr�r�r1rrr r|�s
zIOLoop.add_callbackc
OrQ)
a�
Calls the given callback on the next I/O loop iteration.

        Intended to be afe for use from a Python signal handler; should not be
        used otherwise.

        .. deprecated:: 6.4
           Use ``asyncio.AbstractEventLoop.add_signal_handler`` instead.
           This method is suspected to have been broken since Tornado 5.0 and
           will be removed in version 7.0.
        rRr�rrr �add_callback_from_signal�s
zIOLoop.add_callback_from_signalcOs|j|
g
|�
Ri|�
�

d
S)z�Calls the given callback on the next IOLoop iteration.

        As of Tornado 6.0, this method is equivalent to `add_callback`.

        .. versionadded:: 4.0
        N�
r|r�rrr �spawn_callback�szIOLoop.spawn_callbackrkz0Union[Future[_T], concurrent.futures.Future[_T]]z
Future[_T]csFt|
t
�r|
���
fd
d��

dSt|
�
sJ�
t|
��
fdd��
dS)aA
Schedules a callback on the ``IOLoop`` when the given
        `.Future` is finished.

        The callback is invoked with one argument, the
        `.Future`.

        This method only accepts `.Future` objects and not other
        awaitables (unlike most of Tornado where the two are
        interchangeable).
        c

s�
�t
��|��
Sr)�
_run_callback�	functools�partial�
�
f�r�rrr rn�sz#IOLoop.add_future.<locals>.<lambda>c

s�
��|�Srr�r�r�rr rn�sN)r4rZadd_done_callbackrr)rrkr�rr�r rr�s
	
�zIOLoop.add_future�executor.csj|
d
urt|d�sddl
m}
tjj|�dd�
|_|j}
|
j|g
|�
R�}t��|�	|�f
dd��
�S)	z�Runs a function in a ``concurrent.futures.Executor``. If
        ``executor`` is ``None``, the IO loop's default executor will be used.

        Use `functools.partial` to pass keyword arguments to ``func``.

        .. versionadded:: 5.0
        N�	_executorr
)
�	cpu_count�)
�max_workersc

s
t|��Sr)
rr��
Zt_futurerr rn�s
z(IOLoop.run_in_executor.<locals>.<lambda>)
�hasattrZtornado.processr��
concurrent�futuresZThreadPoolExecutorr�Zsubmitrrr)rr�rhr�r�Zc_futurerr�r �run_in_executor�s



�


zIOLoop.run_in_executorcCs
|
|_d
S)zfSets the default executor to use with :meth:`run_in_executor`.

        .. versionadded:: 5.0
        N)
r�)rr�rrr �set_default_executor�s
zIOLoop.set_default_executorcCs�z.|
�}|d
u
r,ddlm
}
z|�|�
}Wn|jy!


YWd
Sw|�||j�
Wd
SWd
Stjy9


Yd
StyJ


t	j
d|
dd�
Yd
Sw)z�Runs a callback with error handling.

        .. versionchanged:: 6.0

           CancelledErrors are no longer logged.
        Nr
)
�gen�Exception in callback %rT�
rq)Ztornador�rmZ
BadYieldErrorrr�_discard_future_resultrGZCancelledErrorror�error)rr��retr�rrr r��s 




��


�zIOLoop._run_callbackcCs|
��
d
S)z;Avoid unhandled-exception warnings from spawned coroutines.N)
rs)rrkrrr r�szIOLoop._discard_future_resultcCst|
t
�r	|
|
fS|
��|
fSr)r4r(r!rdrrr �split_fds


zIOLoop.split_fdcCs>zt|
t
�rt�|
�

WdS|
��
WdSty


YdSwr)r4r(�osr#�OSErrorrdrrr �close_fd&s




�zIOLoop.close_fdr�cC�|j�
|
�

dSr)�_pending_tasks�add�rr�rrr �_register_task:�
zIOLoop._register_taskcCr�r)r��discardr�rrr �_unregister_task=r�zIOLoop._unregister_task)rr,r$)
T)
Fr)Jr%r&r'�__doc__ZNONEZREADZWRITE�ERROR�dictrH�setr��classmethodr
r:�staticmethodr?rArCry�overloadr>r{rr@rPrBrTrUrr	rWrYrZr#r(rr`r*rrrbrerfrg�floatr�r~r�r��objectr}r�r�rr|r�r�rrr�r�ZExecutorr)r�r�r�rr�rr�r�r�r��
__classcell__rrr<r r,Hs*

N




�
��








,







�
�
��

�
�
��

�
�
�
�	
	

W����
�)
�
�
�
�
�
�
�
�
�
�	
�
�
�
�	��
�!
�
��
�

�
�r,c@s^eZ
dZd
Zgd�
Zdedegdfdeddfdd	�Zd
dde	fdd�Z
d
dde	fd
d�ZdS)�_Timeoutz2An IOLoop timeout, a UNIX timestamp and a callback)r�r��	tdeadliner�r�N�io_looprcCs8t|
t
j�std
|
�
�
|
|_||_|
t|j�
f|_dS)Nr�)	r4r�r�r�r�r��nextZ_timeout_counterr�)rr�r�r�rrr �__init__Gs




�z_Timeout.__init__�othercCs|j|
jkSr�
r��rr�rrr �__lt__W�
z_Timeout.__lt__cCs|j|
jk
Srr�r�rrr �__le__Zr�z_Timeout.__le__)r%r&r'r��	__slots__r�rr,r�r{r�r�rrrr r�As

�

�
�
�r�c	@s�eZ
dZd
Z	ddegeefdeej	e
fde
ddfdd	�Zdd
d�Zddd
�Z
defdd�Zddd�Zddd�Zde
ddfdd�ZdS)�PeriodicCallbacka�Schedules the given callback to be called periodically.

    The callback is called every ``callback_time`` milliseconds when
    ``callback_time`` is a float. Note that the timeout is given in
    milliseconds, while most other time-related functions in Tornado use
    seconds. ``callback_time`` may alternatively be given as a
    `datetime.timedelta` object.

    If ``jitter`` is specified, each callback time will be randomly selected
    within a window of ``jitter * callback_time`` milliseconds.
    Jitter can be used to reduce alignment of events with similar periods.
    A jitter of 0.1 means allowing a 10% variation in callback time.
    The window is centered on ``callback_time`` so the total number of calls
    within a given interval should not be significantly affected by adding
    jitter.

    If the callback runs for longer than ``callback_time`` milliseconds,
    subsequent invocations will be skipped to get back on schedule.

    `start` must be called after the `PeriodicCallback` is created.

    .. versionchanged:: 5.0
       The ``io_loop`` argument (deprecated since version 4.1) has been removed.

    .. versionchanged:: 5.1
       The ``jitter`` argument is added.

    .. versionchanged:: 6.2
       If the ``callback`` argument is a coroutine, and a callback runs for
       longer than ``callback_time``, subsequent invocations will be skipped.
       Previously this was only true for regular functions, not coroutines,
       which were "fire-and-forget" for `PeriodicCallback`.

       The ``callback_time`` argument now accepts `datetime.timedelta` objects,
       in addition to the previous numeric milliseconds.
    r
r��
callback_time�jitterrNcCsR|
|_t
|tj�r|tjd
d�
|_n|dk
rtd�
�
||_||_d|_d|_dS)Nr-)
Zmillisecondsr
z4Periodic callback must have a positive callback_timeF)	r�r4r�r�r��
ValueErrorr��_running�_timeout)rr�r�r�rrr r��s







zPeriodicCallback.__init__c

Cs(t�
�|_d
|_|j��|_|��
dS)zStarts the timer.TN)r,r>r�r�r~�
_next_timeout�_schedule_nextrrrr rf�s



zPeriodicCallback.startc

Cs,d
|_|j
du
r|j�|j
�

d|_
dSdS)zStops the timer.FN)r�r�r�rrrrr rg�s





�zPeriodicCallback.stopc


Cs|jS)
zfReturns ``True`` if this `.PeriodicCallback` has been started.

        .. versionadded:: 4.1
        )
r�rrrr �
is_running�szPeriodicCallback.is_runningc
�s��
|jsdSz4z|�
�}
|
du
rt|
�
r|
IdH
Wnty,


tjd
|j
dd�
YnwW|��
dSW|��
dS|��
w)Nr�Tr�)r�r�rrorr�r�)r�valrrr �_run�s�






�

���zPeriodicCallback._runc

Cs2|jr|�
|j���

|j�|j|j�|_dSdSr)r��_update_nextr�r~r}r�r�r�rrrr r��s


�zPeriodicCallback._schedule_next�current_timecCsp|jd
}|j
r|d|j
t��d9}|j|
k
r/|jt�|
|j|�
d|7_dS|j|7_dS)Ng@�@r-g�?)r�r��randomr��math�floor)rr�Zcallback_time_secrrr r��s






�zPeriodicCallback._update_next)
r
r$)r%r&r'r�rrrrr�r�r�r�rfrgr{r�r�r�r�rrrr r�^s$
)����
�




r�)2r�rG�concurrent.futuresr�r�r�r�r�rpr~r�r�rM�inspectrZtornado.concurrentrrrrrZtornado.logrZtornado.utilr	r
rryrr
rrrrrrrzrrrrZtyping_extensionsrr�rr)r*r,r�r�rrrr �<module>
sB












(


~