Implement PeerDAS RPC handlers#6237
Conversation
dc6a186 to
42de037
Compare
|
Oops I thought this was the first PR in the conga line and incorrectly set the base branch to |
|
I've merged latest base branch into this branch so i can extend the conga line. |
| @@ -320,14 +320,53 @@ impl<T: BeaconChainTypes> NetworkBeaconProcessor<T> { | |||
| pub fn handle_data_columns_by_root_request( | |||
There was a problem hiding this comment.
should this use terminate_response_stream like we use in other similar methods?
| self.log, | ||
| "Received DataColumnsByRoot Request"; | ||
| "peer" => %peer_id, | ||
| "request" => ?request.group_by_ordered_block_root(), |
There was a problem hiding this comment.
what is the benefit of ordering by block roots in this log?
There was a problem hiding this comment.
I introduced group_by_ordered_block_root originally to handle the reprocessing of requests. I left it here as it produces a more succint output. The raw request repeats the root for every column. Usually peers requests multiple indexes for the same root, so the output of this is nicer.
realbigsean
left a comment
There was a problem hiding this comment.
one small suggestion and one question but looks good
25c1647 to
34f796d
Compare
|
@jimmygchen I have forced push a rebase of this branch against unstable, as the commit from #6238 had leaked into this PR |
…erdas-network-rpc-handler
|
@mergify queue |
🛑 The pull request has been removed from the queue
|
|
@mergify refresh |
✅ Pull request refreshed |
|
@mergify queue |
🛑 The pull request has been removed from the queue
|
|
@mergify dequeue |
☑️ The pull request is not queued |
|
@mergify queue |
🛑 The pull request has been removed from the queue
|
|
@mergify requeue |
✅ This pull request will be re-embarked automaticallyDetailsThe followup |
✅ The pull request has been merged automaticallyDetailsThe pull request has been merged automatically at 6566705 |
* Implement PeerDAS RPC handlers * use terminate_response_stream * Merge branch 'unstable' of https://github.com/sigp/lighthouse into peerdas-network-rpc-handler * cargo fmt
* Implement PeerDAS RPC handlers * use terminate_response_stream * Merge branch 'unstable' of https://github.com/sigp/lighthouse into peerdas-network-rpc-handler * cargo fmt
Issue Addressed
Continue porting network changes of
dasbranch. Extends #6238Part of
all branches are on the sipg/lighthouse repo to start another PR conga :)
Proposed Changes
data_columns_by_rootanddata_columns_by_range.Upstream PRs:
DataColumnSidecarsByRootreq/resp protocol #5196