<|h 8dZddlZddlmZdgZGddeZy)z( Native thread-based hostname resolver. N)get_hubResolvercBeZdZdZd dZdZdZdZdZdZ d Z d Z y) ra Implementation of the resolver API using native threads and native resolution functions. Using the native resolution mechanisms ensures the highest compatibility with what a non-gevent program would return including good support for platform specific configuration mechanisms. The use of native (non-greenlet) threads ensures that a caller doesn't block other greenlets. This implementation also has the benefit of being very simple in comparison to :class:`gevent.resolver_ares.Resolver`. .. tip:: Most users find this resolver to be quite reliable in a properly monkey-patched environment. However, there have been some reports of long delays, slow performance or even hangs, particularly in long-lived programs that make many, many DNS requests. If you suspect that may be happening to you, try the dnspython or ares resolver (and submit a bug report). Nc| t}|j|_tj|j vr4|xj tjtj fz c_yyN)r threadpoolpool_socketgaierror NOT_ERRORherror)selfhubs U/var/www/html/test/engine/venv/lib/python3.12/site-packages/gevent/resolver/thread.py__init__zResolver.__init__$sO ;)CNN   3== 0 MMg..? ?M 1cdt|jt|jt||jfzS)Nz<%s.%s at 0x%x pool=%r>)type __module____name__idr rs r__repr__zResolver.__repr__-s=(DJ,A,A,0J,?,?,.tHdii,AA Arcyrrs rclosezResolver.close2s rcV|jjtj|Sr)r applyr gethostbynamerargss rrzResolver.gethostbyname8syyw44d;;rcV|jjtj|Sr)r rr gethostbyname_exr s rr#zResolver.gethostbyname_ex;syyw77>>rcX|jjtj||Sr)r rr getaddrinforr!kwargss rr%zResolver.getaddrinfo>yyw22D&AArcX|jjtj||Sr)r rr gethostbyaddrr&s rr*zResolver.gethostbyaddrAsyyw44dFCCrcX|jjtj||Sr)r rr getnameinfor&s rr,zResolver.getnameinfoDr(rr) rr __qualname____doc__rrrrr#r%r*r,rrrrr s4,@A  <?BDBr)r.r gevent.hubr__all__objectrrrrr2s) ,8Bv8Br