-
Notifications
You must be signed in to change notification settings - Fork 293
feat(iroh)!: Emit mDNS expiry events #3409
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
Open
oscartbeaumont
wants to merge
9
commits into
n0-computer:main
Choose a base branch
from
oscartbeaumont:mdns-expiry
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
b382476
mdns expiry
oscartbeaumont c1ce6f6
wip tests
oscartbeaumont fc3e87a
Merge branch 'main' into mdns-expiry
oscartbeaumont cae97e3
fix unit test
oscartbeaumont e0c5091
Merge remote-tracking branch 'origin' into mdns-expiry
oscartbeaumont 4f297df
fix comment
oscartbeaumont 88b50fd
Merge remote-tracking branch 'origin' into mdns-expiry
oscartbeaumont 085f315
add expiry to static provider
oscartbeaumont a78e6b8
Merge branch 'main' into mdns-expiry
oscartbeaumont 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 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
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
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
Oops, something went wrong.
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.
I think resolve is specifically to find a
DiscoveryItem
or not, would this conceivably ever need to returnDiscoveryEvent::Expired
(or whatever colour that bikesheds ends up having)?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.
My understanding was
resolve
is scoped to a single node wheresubscribe
is for getting the events for every node.If that is correct then personally I think
DiscoveryEvent
here makes sense, if not we could concider changing it back but personally I think that feels a little inconsistent.I suppose the method's name being
resolve
doesn't fit the best with the new return type.I'm happy to do whatever you think here, but personally I think we leave it or concider renaming
resolve
to something else.Uh oh!
There was an error while loading. Please reload this page.
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.
Hi hi!
resolve
should still return aDiscoveryItem
.subscribe
makes sense to return a stream of events, butresolve
should never need to return an expired event. If aNodeId
can no longer be resolved, it should returnNone
.I don't fully understand what would be inconsistent. If you mean, it seems cleaner to have the same return type in both
resolve
andsubscribe
methods, I think that it is not only fine to have different return types, but could be better in some ways. It would more clearly show, just by the function signature, that the methods have different purposes.But let me know if you were referring to something else!
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.
resolve
is meant to be a request for a single node. The reason it returns a stream is because a discovery service might be using multiple queries behind the scenes and different results may come in at different times. iroh wants to start using the first result as soon as possible, but if later results are better still have them available. But this stream is not used for a "long" time.Hence it makes more sense to leave this as a
DiscoveryItem
.