Skip to content
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

Cleanup: Remove fallback node scanner #882

Merged
merged 1 commit into from
Sep 12, 2024
Merged

Conversation

agners
Copy link
Collaborator

@agners agners commented Sep 12, 2024

The fallback node scanner introduced with #603 intents to pick up nodes which our zeroconf scanner missed. There is currently no indication that the zeroconf scanner misses nodes (anymore), so the fallback scanner is redundant. This PR removes the fallback scanner.

The fallback node scanner introduced with #603 intents to pick up nodes
which our zeroconf scanner missed. There is currently no indication
that the zeroconf scanner misses nodes (anymore), so the fallback
scanner is redundant. This PR removes the fallback scanner.
@agners agners added the maintenance Code (quality) improvement or small enhancement which not a new feature label Sep 12, 2024
@agners
Copy link
Collaborator Author

agners commented Sep 12, 2024

I've searched for logs with discovered using fallback ping. There are some reports, such as this community post. But it seems that in this case the same node has been discovered through mDNS as well, but just refuses to setup correctly. So I don't think the fallback does add any value today, especially since we have #873 in place.

@marcelveldt marcelveldt changed the title Remove fallback node scanner Cleanup: Remove fallback node scanner Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Code (quality) improvement or small enhancement which not a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants