-
Notifications
You must be signed in to change notification settings - Fork 923
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
feat(discovery)!: discover peers by tag #2730
Conversation
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.
only basic understanding of how this all works so take my review with grain of salt, but beautiful ❤️
# Conflicts: # share/p2p/discovery/options.go
Codecov Report
@@ Coverage Diff @@
## main #2730 +/- ##
==========================================
- Coverage 51.73% 51.49% -0.24%
==========================================
Files 161 167 +6
Lines 10826 10758 -68
==========================================
- Hits 5601 5540 -61
- Misses 4731 4737 +6
+ Partials 494 481 -13
|
715fc25
to
fc879f7
Compare
79ec3ef
to
4a2bff3
Compare
i didnt know i could double approve like that lol |
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.
Ok, so this is pretty simple. For multiple discoveries we will need something like DiscoveryManager for Discovery CRUD
- fix params validation - update test to use Start/Advertise api instead of passing special values params
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.
Making tag required makes sense
Allow to run multiple discovery subcomponents, where each can find new peers based on preset
tag
and notify its subscribers. It could allow any sort of separate discovery subcomponents (versioned, pruned/archived, etc). Essentially it allows discovery to be abstracted away and act as single function component.Involves some minor refactoring here and there just to clean up things.
Resolves #2578