This repository was archived by the owner on Feb 18, 2021. It is now read-only.
Affinity change vs refresh #91
Merged
Conversation
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
added 5 commits
October 26, 2015 16:39
…rkers from toConnect
jcorbin
force-pushed
the
affinity_change_vs_refresh
branch
from
c6cbdcb to
a0c0b44
Compare
|
Disentangled from #90, since its in test-break hell. |
added 2 commits
October 26, 2015 17:07
…inity refresh from affinity change
jcorbin
force-pushed
the
affinity_change_vs_refresh
branch
from
a0c0b44 to
1a2b2cc
Compare
There was a problem hiding this comment.
indeed, it's here to be used by a future peer.drain such as #90
|
Reviewed things on commits. |
|
🆗 |
|
lgtm. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
connectedServicePeersindexr @Raynos @kriskowal