8000 ServiceStateChange.Updated is being called for NSEC records · Issue #1328 · python-zeroconf/python-zeroconf · GitHub
[go: up one dir, main page]
Skip to content

ServiceStateChange.Updated is being called for NSEC records #1328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
bdraco opened this issue Dec 13, 2023 · 1 comment
Open

ServiceStateChange.Updated is being called for NSEC records #1328

bdraco opened this issue Dec 13, 2023 · 1 comment
Labels
traffic-reduction

Comments

@bdraco
Copy link
Member
bdraco commented Dec 13, 2023 
WARNING:zeroconf._services.browser:Updated non address record=record[nsec,in-unique,Onelink Safe Sound 13F0._hap._tcp.local.]=4500.0/4499,Onelink Safe Sound 13F0._hap._tcp.local.,txt|srv for _hap._tcp.local. Onelink Safe Sound 13F0._hap._tcp.local.
WARNING:zeroconf._services.browser:Enqueueing ServiceStateChange.Updated for _hap._tcp.local. Onelink Safe Sound 13F0._hap._tcp.local.

We shouldn't trigger updates for NSEC records as it means the lack of existence of data. This behavior changed in 0.36 by accident
@bdraco
Copy link
Member Author
bdraco commented Dec 13, 2023

It really doesn't matter so much until we solve #821

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
traffic-reduction
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bdraco
0