-
Notifications
You must be signed in to change notification settings - Fork 1k
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(mdns): emit ToSwarm::NewExternalAddrOfPeer
#5623
Closed
Closed
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b04e4aa
feat(mdns): emit `ToSwarm::NewExternalAddrOfPeer`
wlynxg 6ad00f9
Merge branch 'master' into issue-5104
jxs 9d1a02e
style: optimize code format
58f77a5
style: optimize code format
e98e05d
fix: change `ToSwarm::NewExternalAddrOfPeer` return timing
wlynxg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
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.
why do you prefer having this here instead of after returning discovered addresses?
I feel it's more correct to do this after returning the addresses and maintaining the previous flow of the
pool
loop.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.
Thanks for your comments.
However, my idea here is that
Event::Discovered
andToSwarm::NewExternalAddrOfPeer
events are related.After
Event::Discovered
is returned inrust-libp2p/protocols/mdns/src/behaviour.rs
Line 354 in 9a45db3
poll
will return.When
poll
is entered next time, theNewExternalAddrOfPeer
event will be returned because there is aNewExternalAddrOfPeer
event in the queue.The result is similar to this:
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.
yeah exactly, that's why if we discover multiple addresses we shouldn't return all the
NewExternalAddrOfPeer
events before the second and subsequentEvent::Discovered(discovered)
right?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.
Thank you for your detailed explanation.
I have placed the return time of the
NewExternalAddrOfPeer
event after theEvent::Discovered
event.Please check whether it meets your expectations.