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.
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(lightPush): improve peer usage and improve readability #2155
feat(lightPush): improve peer usage and improve readability #2155
Changes from all commits
4dbb1b6
315d82f
23ded77
240b1b6
ad56eae
7580eeb
800eae2
6bcf283
9742d68
0f09905
3dda8ad
06498f8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
options are not being accounted for in
send
anymoreThere 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.
exactly! as I mentioned here it will be follow up
#2137 (comment)
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.
Did we test this?
So seems like we are not relying on
PeerManager
anymore to retrieve peers to be used for the protocols: moved fromhasPeers()
which relies on PeerManager ->getConnectedPeers()
which gets all available connections, I'm curious how renewing peers would affect management. Wdyt?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.
this is something that was there so I assume we should have tests there
for connections - yes, we move away but not from
hasPeers
but formBaseProtocolSDK.connectedPeers
that proved to be out of sync quite oftenthe reason for it is:
status-go
usage of LightPush that proved to be reliableThere 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.
Yes, I believe
hasPeers
would work with tests. Considering if it would be required to double check withgetConnectedPeers
, especially as we do renewals and what notThere 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.
BaseProtocolSDK.connectedPeers()
was being inconsistent because of race conditions in shared peer management, which isn't the case with #2137