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

Utilize identify events to add peers to the routing table #472

Merged
merged 9 commits into from
Mar 4, 2020

Conversation

aschmahmann
Copy link
Contributor

Uses identify events instead of the notifiee to add peers to the routing table.

This PR is currently based off of the cypress branch, but it may be useful to either base it off of #469 once it's merged or have a subsequent commit to condense the number of goroutines listening to eventbus events.

@aschmahmann aschmahmann self-assigned this Mar 3, 2020
@aschmahmann aschmahmann marked this pull request as ready for review March 4, 2020 02:36
Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small changes but otherwise LGTM.

dht.go Show resolved Hide resolved
subscriber_notifee.go Show resolved Hide resolved
subscriber_notifee.go Show resolved Hide resolved
subscriber_notifee.go Show resolved Hide resolved
subscriber_notifee.go Outdated Show resolved Hide resolved
subscriber_notifee.go Show resolved Hide resolved
Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One nit otherwise LGTM

subscriber_notifee.go Outdated Show resolved Hide resolved
@Stebalien
Copy link
Member

When merging into cypress, let's squash when possible.

@aschmahmann aschmahmann merged commit 2533335 into cypress Mar 4, 2020
Stebalien pushed a commit that referenced this pull request Mar 5, 2020
* feat: consume identify events to evaluate routing table addition
* fix: routing table no longer gets an update just because new messages have arrived or been sent
* fix: add already connected peers into the routing table before listening to events

Co-authored-by: Raúl Kripalani <raul.kripalani@gmail.com>
Co-authored-by: Aarsh Shah <aarshkshah1992@gmail.com>
Stebalien pushed a commit that referenced this pull request Mar 5, 2020
* feat: consume identify events to evaluate routing table addition
* fix: routing table no longer gets an update just because new messages have arrived or been sent
* fix: add already connected peers into the routing table before listening to events

Co-authored-by: Raúl Kripalani <raul.kripalani@gmail.com>
Co-authored-by: Aarsh Shah <aarshkshah1992@gmail.com>
Stebalien pushed a commit that referenced this pull request Apr 3, 2020
* feat: consume identify events to evaluate routing table addition
* fix: routing table no longer gets an update just because new messages have arrived or been sent
* fix: add already connected peers into the routing table before listening to events

Co-authored-by: Raúl Kripalani <raul.kripalani@gmail.com>
Co-authored-by: Aarsh Shah <aarshkshah1992@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants