Up to [cvs.NetBSD.org] / pkgsrc / net / py-zeroconf
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
py-zeroconf: use cython 3.3.0 bugfix from upstream Bump PKGREVISION.
py-zeroconf: adapt PLIST for cython 3.3.0 cython 3.3.0 is more strict in checking signatures, which stops it building the C extension for py-zeroconf. Reported this upstream, remove the .so files from the PLIST for now. Bump PKGREVISION.
py-zeroconf: fix for latest poetry-core Bump PKGREVISION.
py-zeroconf: updated to 0.131.0 v0.131.0 (2023-12-19) Feature * Small speed up to constructing outgoing packets * Speed up processing incoming packets * Speed up the query handler v0.130.0 (2023-12-16) Feature * Make ServiceInfo aware of question history * Small speed up to ServiceInfo construction * Significantly improve efficiency of the ServiceBrowser scheduler * Small speed up to processing incoming records * Small performance improvement for converting time * Small performance improvement for ServiceInfo asking questions * Small performance improvement constructing outgoing questions Fix * Scheduling race with the QueryScheduler * Ensure question history suppresses duplicates * Microsecond precision loss in the query handler * Ensure IPv6 scoped address construction uses the string cache
py-zeroconf: update to 0.127.0. ## v0.127.0 (2023-11-15) ### Feature * Small speed up to writing outgoing packets * Speed up incoming packet reader * Small speed up to processing incoming dns records ## v0.126.0 (2023-11-13) ### Feature * Speed up outgoing packet writer * Speed up writing name compression for outgoing packets ## v0.125.0 (2023-11-12) ### Feature * Speed up service browser queries when browsing many types ## v0.124.0 (2023-11-12) ### Feature * Avoid decoding known answers if we have no answers to give * Small speed up to process incoming packets ## v0.123.0 (2023-11-12) ### Feature * Speed up instances only used to lookup answers ## v0.122.3 (2023-11-09) ### Fix * Do not build musllinux aarch64 wheels to reduce release time ## v0.122.2 (2023-11-09) ### Fix * Do not build aarch64 wheels for PyPy ## v0.122.1 (2023-11-09) ### Fix * Skip wheel builds for eol python and older python with aarch64 ## v0.122.0 (2023-11-08) ### Feature * Build aarch64 wheels ## v0.121.0 (2023-11-08) ### Feature * Speed up record updates ## v0.120.0 (2023-11-05) ### Feature * Speed up incoming packet processing with a memory view * Speed up decoding labels from incoming data * Speed up ServiceBrowsers with a pxd for the signal interface ## v0.119.0 (2023-10-18) ### Feature * Update cibuildwheel to build wheels on latest cython final release ## v0.118.1 (2023-10-18) ### Fix * Reduce size of wheels by excluding generated .c files ## v0.118.0 (2023-10-14) ### Feature * Small improvements to ServiceBrowser performance ## v0.117.0 (2023-10-14) ### Feature * Small cleanups to incoming data handlers
py-zeroconf: updated to 0.116.0 v0.116.0 (2023-10-13) Feature * Reduce type checking overhead at run time v0.115.2 (2023-10-05) Fix * Ensure ServiceInfo cache is cleared when adding to the registry v0.115.1 (2023-10-01) Fix * Add missing python definition for addresses_by_version v0.115.0 (2023-09-26) Feature * Speed up outgoing multicast queue v0.114.0 (2023-09-25) Feature * Speed up responding to queries v0.113.0 (2023-09-24) Feature * Improve performance of loading records from cache in ServiceInfo v0.112.0 (2023-09-14) Feature * Improve AsyncServiceBrowser performance v0.111.0 (2023-09-14) Feature * Speed up question and answer internals v0.110.0 (2023-09-14) Feature * Small speed ups to ServiceBrowser v0.109.0 (2023-09-14) Feature * Speed up ServiceBrowsers with a cython pxd v0.108.0 (2023-09-11) Feature * Improve performance of constructing outgoing queries v0.107.0 (2023-09-11) Feature * Speed up responding to queries v0.106.0 (2023-09-11) Feature * Speed up answering questions v0.105.0 (2023-09-10) Feature * Speed up ServiceInfo with a cython pxd v0.104.0 (2023-09-10) Feature * Speed up generating answers
py-zeroconf: install C extension. Remove unneeded dependency for Python 3.11. Bump PKGREVISION. Fixes PR 57453.
py-zeroconf: fix PLIST
py-zeroconf: updated to 0.47.3 v0.47.3 (2023-02-14) Fix Hold a strong reference to the query sender start task v0.47.2 (2023-02-14) Fix Missing c extensions with newer poetry v0.47.1 (2022-12-24) Fix The equality checks for DNSPointer and DNSService should be case insensitive v0.47.0 (2022-12-22) Feature Optimize equality checks for DNS records v0.46.0 (2022-12-21) Feature Optimize the dns cache v0.45.0 (2022-12-20) Feature Optimize construction of outgoing packets v0.44.0 (2022-12-18) Feature Optimize dns objects by adding pxd files v0.43.0 (2022-12-18) Feature Optimize incoming parser by reducing call stack v0.42.0 (2022-12-18) Feature Optimize incoming parser by using unpack_from v0.41.0 (2022-12-18) Feature Optimize incoming parser by adding pxd files v0.40.1 (2022-12-18) Fix Fix project name in pyproject.toml v0.40.0 (2022-12-17) Feature Drop async_timeout requirement for python 3.11+
py-zeroconf: updated to 0.37.0 0.37.0 Technically backwards incompatible: Adding a listener that does not inherit from RecordUpdateListener now logs an error The NotRunningException exception is now thrown when Zeroconf is not running Before this change the consumer would get a timeout or an EventLoopBlocked exception when calling ServiceInfo.*request when the instance had already been shutdown or had failed to startup. The EventLoopBlocked exception is now thrown when a coroutine times out Previously concurrent.futures.TimeoutError would have been raised instead. This is never expected to happen during normal operation.
py-zeroconf: updated to 0.32.0 0.32.0 This release offers 100% line and branch coverage. Made ServiceInfo first question QU We want an immediate response when requesting with ServiceInfo by asking a QU question; most responders will not delay the response and respond right away to our question. This also improves compatibility with split networks as we may not have been able to see the response otherwise. If the responder has not multicast the record recently, it may still choose to do so in addition to responding via unicast Reduces traffic when there are multiple zeroconf instances running on the network running ServiceBrowsers If we don't get an answer on the first try, we ask a QM question in the event, we can't receive a unicast response for some reason This change puts ServiceInfo inline with ServiceBrowser which also asks the first question as QU since ServiceInfo is commonly called from ServiceBrowser callbacks Limited duplicate packet suppression to 1s intervals Only suppress duplicate packets that happen within the same second. Legitimate queriers will retry the question if they are suppressed. The limit was reduced to one second to be in line with rfc6762 Made multipacket known answer suppression per interface The suppression was happening per instance of Zeroconf instead of per interface. Since the same network can be seen on multiple interfaces (usually and wifi and ethernet), this would confuse the multi-packet known answer supression since it was not expecting to get the same data more than once New ServiceBrowsers now request QU in the first outgoing when unspecified https://datatracker.ietf.org/doc/html/rfc6762#section-5.4 When we start a ServiceBrowser and zeroconf has just started up, the known answer list will be small. By asking a QU question first, it is likely that we have a large known answer list by the time we ask the QM question a second later (current default which is likely too low but would be a breaking change to increase). This reduces the amount of traffic on the network, and has the secondary advantage that most responders will answer a QU question without the typical delay answering QM questions. IPv6 link-local addresses are now qualified with scope_id When a service is advertised on an IPv6 address where the scope is link local, i.e. fe80::/64 (see RFC 4007) the resolved IPv6 address must be extended with the scope_id that identifies through the "%" symbol the local interface to be used when routing to that address. A new API parsed_scoped_addresses() is provided to return qualified addresses to avoid breaking compatibility on the existing parsed_addresses(). Network adapters that are disconnected are now skipped Fixed listeners missing initial packets if Engine starts too quickly When manually creating a zeroconf.Engine object, it is no longer started automatically. It must manually be started by calling .start() on the created object. The Engine thread is now started after all the listeners have been added to avoid a race condition where packets could be missed at startup. Fixed answering matching PTR queries with the ANY query Fixed lookup of uppercase names in the registry If the ServiceInfo was registered with an uppercase name and the query was for a lowercase name, it would not be found and vice-versa. Fixed unicast responses from any source port Unicast responses were only being sent if the source port was 53, this prevented responses when testing with dig: dig -p 5353 @224.0.0.251 media-12.local The above query will now see a response Fixed queries for AAAA records not being answered Removed second level caching from ServiceBrowsers The ServiceBrowser had its own cache of the last time it saw a service that was reimplementing the DNSCache and presenting a source of truth problem that lead to unexpected queries when the two disagreed. Fixed server cache not being case-insensitive If the server name had uppercase chars and any of the matching records were lowercase, and the server would not be found Fixed cache handling of records with different TTLs There should only be one unique record in the cache at a time as having multiple unique records will different TTLs in the cache can result in unexpected behavior since some functions returned all matching records and some fetched from the right side of the list to return the newest record. Instead we now store the records in a dict to ensure that the newest record always replaces the same unique record, and we never have a source of truth problem determining the TTL of a record from the cache. Fixed ServiceInfo with multiple A records If there were multiple A records for the host, ServiceInfo would always return the last one that was in the incoming packet, which was usually not the one that was wanted. Fixed stale unique records expiring too quickly Records now expire 1s in the future instead of instant removal. tools.ietf.org/html/rfc6762#section-10.2 Queriers receiving a Multicast DNS response with a TTL of zero SHOULD NOT immediately delete the record from the cache, but instead record a TTL of 1 and then delete the record one second later. In the case of multiple Multicast DNS responders on the network described in Section 6.6 above, if one of the responders shuts down and incorrectly sends goodbye packets for its records, it gives the other cooperating responders one second to send out their own response to "rescue" the records before they expire and are deleted. Fixed exception when unregistering a service multiple times Added an AsyncZeroconfServiceTypes to mirror ZeroconfServiceTypes to zeroconf.asyncio Fixed interface_index_to_ip6_address not skiping ipv4 adapters Added async_unregister_all_services to AsyncZeroconf Fixed services not being removed from the registry when calling unregister_all_services There was a race condition where a query could be answered for a service in the registry, while goodbye packets which could result in a fresh record being broadcast after the goodbye if a query came in at just the right time. To avoid this, we now remove the services from the registry right after we generate the goodbye packet Fixed zeroconf exception on load when the system disables IPv6 Fixed the QU bit missing from for probe queries The bit should be set per datatracker.ietf.org/doc/html/rfc6762#section-8.1 Fixed the TC bit missing for query packets where the known answers span multiple packets Fixed packets not being properly separated when exceeding maximum size Ensure that questions that exceed the max packet size are moved to the next packet. This fixes DNSQuestions being sent in multiple packets in violation of: datatracker.ietf.org/doc/html/rfc6762#section-7.2 Ensure only one resource record is sent when a record exceeds _MAX_MSG_TYPICAL datatracker.ietf.org/doc/html/rfc6762#section-17 Fixed PTR questions asked in uppercase not being answered Added Support for context managers in Zeroconf and AsyncZeroconf Implemented an AsyncServiceBrowser to compliment the sync ServiceBrowser Added async_get_service_info to AsyncZeroconf and async_request to AsyncServiceInfo Implemented allowing passing in a sync Zeroconf instance to AsyncZeroconf Fixed IPv6 setup under MacOS when binding to "" Fixed ZeroconfServiceTypes.find not always cancels the ServiceBrowser There was a short window where the ServiceBrowser thread could be left running after Zeroconf is closed because the .join() was never waited for when a new Zeroconf object was created Fixed duplicate packets triggering duplicate updates If TXT or SRV records update was already processed and then received again, it was possible for a second update to be called back in the ServiceBrowser Fixed ServiceStateChange.Updated event happening for IPs that already existed Fixed RFC6762 Section 10.2 paragraph 2 compliance Reduced length of ServiceBrowser thread name with many types Fixed empty answers being added in ServiceInfo.request Fixed ServiceInfo not populating all AAAA records Use get_all_by_details to ensure all records are loaded into addresses. Only load A/AAAA records from the cache once in load_from_cache if there is a SRV record present Move duplicate code that checked if the ServiceInfo was complete into its own function Fixed a case where the cache list can change during iteration Return task objects created by AsyncZeroconf Traffic Reduction: Added support for handling QU questions Implements RFC 6762 sec 5.4: Questions Requesting Unicast Responses datatracker.ietf.org/doc/html/rfc6762#section-5.4 Implemented protect the network against excessive packet flooding Additionals are now suppressed when they are already in the answers section Additionals are no longer included when the answer is suppressed by known-answer suppression Implemented multi-packet known answer supression Implements datatracker.ietf.org/doc/html/rfc6762#section-7.2 Implemented efficient bucketing of queries with known answers Implemented duplicate question suppression http://datatracker.ietf.org/doc/html/rfc6762#section-7.3 Technically backwards incompatible: Update internal version check to match docs (3.6+) Python version earlier then 3.6 were likely broken with zeroconf already, however, the version is now explicitly checked. Update python compatibility as PyPy3 7.2 is required Backwards incompatible: Drop oversize packets before processing them Oversized packets can quickly overwhelm the system and deny service to legitimate queriers. In practice, this is usually due to broken mDNS implementations rather than malicious actors. Guard against excessive ServiceBrowser queries from PTR records significantly lowerthan recommended We now enforce a minimum TTL for PTR records to avoid ServiceBrowsers generating excessive queries refresh queries. Apple uses a 15s minimum TTL, however, we do not have the same level of rate limit and safeguards, so we use 1/4 of the recommended value. RecordUpdateListener now uses async_update_records instead of update_record This allows the listener to receive all the records that have been updated in a single transaction such as a packet or cache expiry. update_record has been deprecated in favor of async_update_records A compatibility shim exists to ensure classes that use RecordUpdateListener as a base class continue to have update_record called, however, they should be updated as soon as possible. A new method async_update_records_complete is now called on each listener when all listeners have completed processing updates and the cache has been updated. This allows ServiceBrowsers to delay calling handlers until they are sure the cache has been updated as its a common pattern to call for ServiceInfo when a ServiceBrowser handler fires. The async_ prefix was chosen to make it clear that these functions run in the eventloop and should never do blocking I/O. Before 0.32+ these functions ran in a select() loop and should not have been doing any blocking I/O, but it was not clear to implementors that I/O would block the loop. Pass both the new and old records to async_update_records Pass the old_record (cached) as the value and the new_record (wire) to async_update_records instead of forcing each consumer to check the cache since we will always have the old_record when generating the async_update_records call. This avoids the overhead of multiple cache lookups for each listener.
py-zeroconf: updated to 0.30.0 0.30.0: Unknown changes
py-zeroconf: updated to 0.24.4 0.24.4 Fixed resetting TTL in DNSRecord.reset_ttl() Improved various DNS class' string representations
net/py-zeroconf: import py38-zeroconf-0.24.3 Pure Python Multicast DNS Service Discovery Library