ث Qٌ3jمَئ—UdZddlZddlZddlmZmZmZddlmZddl m Z mZGd„de«ZiZ eeefed<iZeee fed <iZeeefed <ddœd„Zd „Zd„Zd„Zy)aCross-process transport for callback messages. When a callback is registered on an estimator that uses multiple worker processes, every worker ends up with its own copy of the callback (sent there by pickling). However, the user-visible state (e.g. logs being filled in or progress bars advancing) lives on the main process. This module provides a way for the worker copies to ship their messages back to the main process over a local endpoint (a UNIX socket on Unix, a Windows named pipe on Windows). Remark: we don't use a `multiprocessing.Manager` because its proxy objects become unusable once the Manager subprocess is gone, e.g. after unpickling in a fresh interpreter. The only ways to work around that either rely on multiprocessing private API or give up cross-process capabilities. éN)عClientع ConnectionعListener)عThread)عCallableع NamedTuplecَ&—eZdZUdZeed<eed<y)عListenerHandlea•A picklable reference to a main-process listener. Attributes ---------- address : str Address of the local endpoint the listener is bound to. Workers use this to connect, and the main process also uses it as a key into this module's registries to find the live listener. authkey : bytes Shared secret used to authenticate connections to the listener. عaddressعauthkeyN)ع__name__ع __module__ع__qualname__ع__doc__عstrع__annotations__عbytes©َْH/DATA/.local/lib/python3.12/site-packages/sklearn/callback/_transport.pyr r s…ًٌƒLط „Nrr ع _listenersع_message_consumersع_worker_connections)عownercَP‡‡‡—tjd«}t|d¬«ٹt‰j|¬«}‰t |j<‰t|j<|پtj|t|«ˆfd„ٹˆˆfd„}t|d¬«j«|S) aهCreate a listener for incoming messages on the main process. Also registers the listener and its message consumer in the module-level dicts. Parameters ---------- message_consumer : callable A one-argument function, `message_consumer(message)`, that processes incoming message to update the callback's state. This callable may be called from multiple different threads, and must therefore behave in a thread-safe manner. owner : callback instance, default=None Optional owner callback. When provided, the listener is automatically closed when `owner` gets garbage-collected. Returns ------- listener_handle : ListenerHandle A reference to the listener. é é€)rعbacklog)rrcَ‚•— ‰|j««|jd«Œ(#ttf$rYywxYw)N)عrecvعsendعEOFErrorعOSError)عconnعmessage_consumers €rع_handlezopen_listener.._handleisBّ€ً طظ §،£ش-ط— ‘ ک$”ًّôœ'ذ"ٍ ظً ْsƒ),¬>½>cَ‚•— ‰j«}t‰|fd¬«j«Œ/#t$rYywxYw)NT)عtargetعargsعdaemon)عacceptr#rعstart)r$r&عlisteners €€rع_acceptzopen_listener.._accepttsIّ€طً ط—‘س(گô ک'¨¨¸ش=×CرCشEًّôٍ ظً ْs„2² >½>T)r(r*)عosعurandomrr rrrعweakrefعfinalizeعclose_listenerrr,)r%rrعlistener_handler.r&r-s` @@rع open_listenerr5Ds‘ْ€ô*ڈj‰jک‹n€Gô °ش5€Hـ$¨X×-=ر-=ہwشO€Oà*2„Jˆ×&ر&ر'ط2Bشگ×.ر.ر/طذـ×رک¤°ش@ô ُFôگ' $ش'×-ر-ش/طذrcَھ—tj|jd«tj|jd«}|پ|j «yy)zEStop listening for `listener_handle` and free its background threads.N)rعpoprrعclose)r4r-s rr3r3€sC€ن×رک?×2ر2°Dش9ـڈ~‰~کo×5ر5°tس<€Hطذطڈ‰صًrcَ¨—|jtvry t|j|j¬«j «y#t $rYywxYw)a´Whether the listener at `listener_handle` is usable from this process. Helper for callbacks that open their listener eagerly (e.g. in `__init__`) and therefore have to decide, on unpickling, whether to keep the inherited handle or open a fresh listener. The listener is not reusable when: - We are the process that originally opened the listener. Reusing the handle would route messages through the in-process fast path of `send`, into the original instance's message consumer instead of the unpickled instance's. - The listener is no longer reachable, e.g. unpickling in a fresh interpreter, or on a host that cannot reach the original listener. F©rT)rrrrr8r#)r4s rعcan_reuse_listenerr;ˆsR€ً×ر¤*ر,طًـˆ×&ر&°×0Gر0GشH×NرNشPًّôٍظًْs•/Aء AءAcَ —tj|j«}|پ ||«y|j}tj|«}|€ t ||j ¬«}|t|<|j |«|j«y)aنDeliver `message` to whoever is listening on `listener_handle`. There are two possible delivery paths: - In-process fast path: `send` is called in the same process that called `open_listener` for this listener handle. The message consumer can directly be called without any serialization overhead. - Cross-process path: `send` is called in a different process. The worker opens a `Client` connection to the main-process listener on first use and caches it in `_worker_connections`, so all subsequent messages reuse the same socket. `send` then waits for an acknowledgement from the main process so that, by the time it returns, the message has actually been processed by the consumer. Nr:)rعgetrrrrr!r )r4عmessager%rع connections rr!r!ںs€€ô*×-ر-¨o×.Eر.EسFذطذ#ظکش!طà×%ر%€Gـ$×(ر(¨س1€JطذـکG¨_×-Dر-DشEˆ ط'1شکGر$ط‡OپOگGشط‡OپOصr)rr/r1عmultiprocessing.connectionrrrع threadingrعtypingrrr rعdictrrrrr5r3r;r!rrrعrDs„ًٍ َ غكCرCفك'ôگZôًB#%€ ˆDگگhگرس$ط*,ذگDککhکر'س,ً .0ذگTک#کzک/ر*س/ً.2ô9ٍxٍَ.r