§ qٹtjمَà—UdZddlZddlZddlmZmZmZddlmZddl m Z mZGd„de¦«ZiZ eeefed<iZeee fed <iZeeefed <ddœd„Zd „Zd„Zd„ZdS)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<dS)ع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©َْY/var/www/html/CA-Chatbot/venv/lib/python3.11/site-packages/sklearn/callback/_transport.pyr r s.€€€€€€ًًً€L€LپLط €N€NپN€N€Nrr ع _listenersع_message_consumersع_worker_connections)عownercَT‡‡‡—tjd¦«}t|d¬¦«ٹt‰j|¬¦«}‰t |j<‰t|j<|پtj|t|¦«ˆfd„ٹˆˆfd„}t|d¬ ¦« ¦«|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)rrNcَ‍•— ‰| ¦«¦«| d¦«Œ3#ttf$rYdSwxYw)N)عrecvعsendعEOFErrorعOSError)عconnعmessage_consumers €rع_handlezopen_listener.._handleiscّ€ً ً ط ذ §¢،¤ر-ش-ذ-ط— ’ ک$‘”گً ُّ‌'ذ"ً ً ً طˆFˆFً ّّّsƒ47·AءAcَ •— ‰ ¦«}n#t$rYdSwxYwt‰|fd¬¦« ¦«ŒM)NT)عtargetعargsعdaemon)عacceptr#rعstart)r$r&عlisteners €€rع_acceptzopen_listener.._accepttsjّ€ً Fً ط—’ر(ش(گگّفً ً ً طگگً ّّّهک'¨¨¸ذ=ر=ش=×CزCرEشEذEً Fs„™ '¦'T)r(r*)عosعurandomrr rrrعweakrefعfinalizeعclose_listenerrr,)r%rrعlistener_handler.r&r-s` @@rع open_listenerr5Ds×ّّّ€ُ*Œjک‰nŒn€Gُ °ذ5ر5ش5€Hف$¨Xش-=ہwذOرOشO€Oà*2…Jˆش&ر'ط2Bصگش.ر/طذفشک¥°ر@ش@ذ@ً ً ً ً ً ًFًFًFًFًFًFُگ' $ذ'ر'ش'×-ز-ر/ش/ذ/طذrcَ¶—t |jd¦«t |jd¦«}|پ| ¦«dSdS)zEStop listening for `listener_handle` and free its background threads.N)rعpoprrعclose)r4r-s rr3r3€sU€ه×زک?ش2°Dر9ش9ذ9فڈ~ٹ~کoش5°tر<ش<€Hطذطڈٹرشذذذًذrcَ¦—|jtvrdS t|j|j¬¦« ¦«n#t $rYdSwxYwdS)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;ˆsk€ًش¥*ذ,ذ,طˆuًفˆش&°ش0GذHرHشH×NزNرPشPذPذPّفًًًطˆuˆuًّّّàˆ4s’-Aء Aء Acَ:—t |j¦«}|پ ||¦«dS|j}t |¦«}|€ t ||j¬¦«}|t|<| |¦«| ¦«dS)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رFشFذطذ#طذکر!ش!ذ!طˆàش%€Gف$×(ز(¨ر1ش1€JطذفکG¨_ش-DذEرEشEˆ ط'1صکGر$ط‡O‚OگGرشذط‡O‚Oرشذذذr)rr/r1عmultiprocessing.connectionrrrع threadingrعtypingrrr rعdictrrrrr5r3r;r!rrrْrDsBًً ً ً ً € € € ط€€€طCذCذCذCذCذCذCذCذCذCطذذذذذط'ذ'ذ'ذ'ذ'ذ'ذ'ذ'ًًًًًگZٌôًًB#%€ ˆDگگhگشذ$ذ$ر$ط*,ذگDککhکش'ذ,ذ,ر,ً .0ذگTک#کzک/ش*ذ/ذ/ر/ً.2ً9ً9ً9ً9ً9ًxًًًًًً.ًًًًr