Watch Windows interface lifecycle changes - #24
Merged
Conversation
thombles
force-pushed
the
windows-adapter-change
branch
5 times, most recently
from
July 26, 2026 10:27
07c8764 to
4cf1ef1
Compare
thombles
changed the title
thombles
force-pushed
the
windows-adapter-change
branch
from
July 26, 2026 10:43
7622010 to
2250cc0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #14.
Adds a Windows-only integration test that installs a disposable Microsoft KM-TEST Loopback Adapter and verifies that both callback and queued/blocking watchers report the address-free interface being added and removed as it is enabled and disabled.
The Windows backend now subscribes to both unicast address changes and IP interface changes. Both notification paths refresh through the existing snapshot and diff machinery, which deduplicates overlapping notifications.