-
Notifications
You must be signed in to change notification settings - Fork 690
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
new routing exchange prototype using IBF #4112
new routing exchange prototype using IBF #4112
Conversation
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.
Need to add integration tests that stress different scenarios of synchronization using IBF.
This PR has been automatically marked as stale because it has not had recent activity in the 2 weeks. |
@pmnoxx what is the status here? |
I submitted updated PR. You can take a look. |
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.
jsonrpc endpoints not follows the way we are handing endpoints. Please, make them as the other endpoints.
This PR has been automatically marked as stale because it has not had recent activity in the 2 weeks. |
@pmnoxx what is the status of this PR? |
This PR has been automatically marked as stale because it has not had recent activity in the 2 weeks. |
This PR has been automatically marked as stale because it has not had recent activity in the 2 weeks. |
What is the status on this PR? It has again been marked staled? Do we still plan to land this? Can we close it? @pmnoxx @bowenwang1996 |
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.
OK for stable hash change.
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.
There's not a lot change in runtime, and these changes look okay. As for the IBF in network and chain, I studied and felt confident it's a correct implementation too. I particularly like the unit tests, the benchmark and the pytest, together they prove the correctness and scale in orthogonal ways.
Ok, I addressed the issues you mentioned
Nayduck passes previously. I ran it one more time after doing all changes: All tests pass |
@frol Is there anything that prevents us from merging? |
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 am unblocking this PR from merging, so I am not blocking merging it once all my comments are addressed.
…te (#4912) #4651 successfully removed `near-jsonrpc-primitives`-s heavy dependency on `near-network` which in turn depended on `rocksdb`. #4112 reintroduced that dependency on `near-network`, though optionally, this hinders the publishing process. This PR extracts the adversarial features that depend on `near-network` into a private, specialized crate: `near-jsonrpc-adversarial-primitives` and sets us right on track for publishing `jsonrpc-primitives`.
Implement new algorithm for exchanging routing tables using Inverse Bloom Filters.
#3838
Reposting #4108