-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Fix SSDP/UPnP server after testing #80 8000 815
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.
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
Fix SSDP/UPnP server after testing #80815
Conversation
Converted to draft, as |
I have verified that HTTP and SSDP servers starts on macOS with this change. I also see incoming and outgoing communication on SSDP multicast on both IPv4 and IPv6, both for discovery and for the server, and I can reach the HTTP servers on both IPv4 and IPv6. |
Tested and verified the reported race is gone on macos and linux |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. One question above #80815 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Retested 👍
Great, thanks! |
Proposed change
Fixes after testing by @oyvindwe the new ssdp/upnp server. Includes a fix for the race condition reported in #80400 as well.
Type of change
Additional information
Changes to
async-upnp-client
0.32.1
:Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: