We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@dignifiedquire commented on Sat Apr 01 2017
@jayarjo commented on Wed Apr 03 2019
Why do you folks keep issues for merged fixes open?
@JustMaier commented on Sun Jun 02 2019
Doesn't look like this has been implemented yet, which appears to mean that the js peer-book isn't at parity with the go peer-book.
@tapaswenipathak commented on Sat Jul 27 2019
Hi folks: Can I take the ticket?
@JustMaier commented on Mon Jul 29 2019
@tapaswenipathak that'd be awesome!
The text was updated successfully, but these errors were encountered:
FYI we now have the PeerStore decoupled into AddressBook, ProtoBook, KeyBook and MetadataBook. We can easily move forward with this issue
Sorry, something went wrong.
Closed as implemented. An application can record latency information in the metadata section of the peer store
No branches or pull requests
@dignifiedquire commented on Sat Apr 01 2017
@jayarjo commented on Wed Apr 03 2019
Why do you folks keep issues for merged fixes open?
@JustMaier commented on Sun Jun 02 2019
Doesn't look like this has been implemented yet, which appears to mean that the js peer-book isn't at parity with the go peer-book.
@tapaswenipathak commented on Sat Jul 27 2019
Hi folks: Can I take the ticket?
@JustMaier commented on Mon Jul 29 2019
@tapaswenipathak that'd be awesome!
The text was updated successfully, but these errors were encountered: