U [e@sddlZddlZddlmZddlmZddlmZmZddl m Z ddl m Z m Z mZddlmZmZddlmZd d lmZmZmZmZmZGd d d ZdddZGdddZGdddZGdddeZdS)N)count)Optional) AuthenticatorBEGIN)get_bus)Message MessageTypeParser) ProxyBase unwrap_msg) message_bus)MessageFilters FilterHandle ReplyMatcher RouterClosedcheck_replyablec@s^eZdZdZejejdddZddeddd Z ed d d Z d dZ ddZ ddZ dS)DBusConnectionaPA plain D-Bus connection with no matching of replies. This doesn't run any separate tasks: sending and receiving are done in the task that calls those methods. It's suitable for implementing servers: several worker tasks can receive requests and send replies. For a typical client pattern, see :class:`DBusRouter`. )readerwritercCs4||_||_t|_tdd|_d|_t|_ dS)Nr )start) rrr parserroutgoing_serial unique_nameasyncioLock send_lock)selfrrrT/var/www/html/services/stratfitenv/lib/python3.8/site-packages/jeepney/io/asyncio.py__init__s  zDBusConnection.__init__Nserial)messagec sX|j4IdH:|dkr"t|j}|j|||jIdHW5QIdHRXdS)z.Serialise and send a :class:`~.Message` objectN)rnextrrwriteZ serialisedrainrr#r"rrrsend s  zDBusConnection.sendreturncsB|j}|dk r|S|jdIdH}|s0t|j|qdS)z5Return the next available message from the connectionNi)rZget_next_messagerreadEOFErrorZadd_data)rmsgbrrrreceive(s zDBusConnection.receivecs|j|jIdHdS)zClose the D-Bus connectionN)rclose wait_closedrrrrr04s zDBusConnection.closecs|SNrr2rrr __aenter__9szDBusConnection.__aenter__cs|IdHdSr3)r0rexc_typeexc_valexc_tbrrr __aexit__<szDBusConnection.__aexit__)__name__ __module__ __qualname____doc__r StreamReader StreamWriterr rr(r/r0r4r9rrrrrs rSESSIONc st|}t|IdH\}}t}|D]B}|||IdH|dIdH}|s^td||q&|t |IdHt ||}t |4IdH,}t t t|dIdH} | d|_W5QIdHRX|S)zHOpen a plain D-Bus connection :return: :class:`DBusConnection` Niz#Socket closed before authentication r)rropen_unix_connectionrr%r&r+r,feedrr DBusRouterwait_forProxyr ZHellor) busZbus_addrrrZauthrZreq_datar.connrouterZ reply_bodyrrropen_dbus_connection@s"    rJc@seZdZdZdZdZdZedddZe ddZ ddd d Z e d d d Z dddeejdddZddZddZe dddZddZdS)rDzA 'client' D-Bus connection which can wait for a specific reply. This runs a background receiver task, and makes it possible to send a request and wait for the relevant reply. N)rHcCs*||_t|_t|_t||_dSr3) _connr_repliesr_filtersr create_task _receiver _rcv_task)rrHrrrr jszDBusRouter.__init__cCs|jjSr3)rKrr2rrrrpszDBusRouter.unique_namer!cs|jj||dIdHdS)z&Send a message, don't wait for a replyr!N)rKr(r'rrrr(tszDBusRouter.sendr)c snt||jrtdt|jj}|j|t ,}|j ||dIdH|IdHW5QRSQRXdS)zSend a method call message and wait for the reply Returns the reply message (method return or error message type). zThis DBusRouter has stoppedr!N) rrPdonerr$rKrrLZcatchrFuturer()rr#r"Z reply_futrrrsend_and_get_replyxs  zDBusRouter.send_and_get_replyr )queuebufsize)rTcCst|j||pt|S)arCreate a filter for incoming messages Usage:: with router.filter(rule) as queue: matching_msg = await queue.get() :param MatchRule rule: Catch messages matching this rule :param asyncio.Queue queue: Send matching messages here :param int bufsize: If no queue is passed in, create one with this size )rrMrQueue)rrulerTrUrrrfilters zDBusRouter.filtercs|Sr3rr2rrrr4szDBusRouter.__aenter__c sH|jr|jn.|jttj|jIdHW5QRXdS)NF)rPrQresultcancel contextlibsuppressrCancelledErrorr5rrrr9s    zDBusRouter.__aexit__)r-c CsR|j|rdSt|j|D],}z|j|Wq tjk rJYq Xq dS)zHandle one received messageN) rLdispatchlistrMmatchesrT put_nowaitr QueueFull)rr-rXrrr _dispatchs zDBusRouter._dispatchcs2z |jIdH}||qW5|jXdS)z'Receiver loop - runs in a separate taskN)rLZdrop_allrKr/rc)rr-rrrrOszDBusRouter._receiver)r:r;r<r=Z _nursery_mgrZ_send_cancel_scopeZ_rcv_cancel_scoperr propertyrr(rrSrrrVrXr4r9rcrOrrrrrD`s   rDc@s2eZdZdZdZdZd ddZddZdd ZdS) open_dbus_routerzOpen a D-Bus 'router' to send and receive messages Use as an async context manager:: async with open_dbus_router() as router: ... Nr@cCs ||_dSr3)rG)rrGrrrr szopen_dbus_router.__init__cs.t|jIdH|_t|j|_|jIdHSr3)rJrGrHrDreq_ctxr4r2rrrr4s zopen_dbus_router.__aenter__cs*|j|||IdH|jIdHdSr3)rfr9rHr0r5rrrr9szopen_dbus_router.__aexit__)r@) r:r;r<r=rHrfr r4r9rrrrres  recs0eZdZdZfddZddZddZZS)rFaAn asyncio proxy for calling D-Bus methods You can call methods on the proxy object, such as ``await bus_proxy.Hello()`` to make a method call over D-Bus and wait for a reply. It will either return a tuple of returned data, or raise :exc:`.DBusErrorResponse`. The methods available are defined by the message generator you wrap. :param msggen: A message generator object. :param ~asyncio.DBusRouter router: Router to send and receive messages. cst|||_dSr3)superr _router)rZmsggenrI __class__rrr s zProxy.__init__cCsd|j|jS)Nz Proxy({}, {}))formatZ_msggenrhr2rrr__repr__szProxy.__repr__csfdd}|S)Ncs6||}|jjtjkstj|IdH}t|Sr3)headerZ message_typer method_callAssertionErrorrhrSr )argskwargsr-Zreplymake_msgrrrinners z!Proxy._method_call..innerr)rrsrtrrrr _method_callszProxy._method_call)r:r;r<r=r rlru __classcell__rrrirrFs rF)r@)rr[ itertoolsrtypingrZ jeepney.authrrZ jeepney.busrZjeepneyrrr Zjeepney.wrappersr r Zjeepney.bus_messagesr commonrrrrrrrJrDrerFrrrrs    0 X