-
Notifications
You must be signed in to change notification settings - Fork 784
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
Restore Log on Error & Spawn Blocking in Streamer #5585
Restore Log on Error & Spawn Blocking in Streamer #5585
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.
I like the logging message structure being standard across all these responses, howeve looks like blobs by root was missed because it required no other logging change, could I request its message be updated to:
BlobsByRoot outgoing response processed
beacon_node/network/src/network_beacon_processor/rpc_methods.rs
Outdated
Show resolved
Hide resolved
beacon_node/network/src/network_beacon_processor/rpc_methods.rs
Outdated
Show resolved
Hide resolved
beacon_node/network/src/network_beacon_processor/rpc_methods.rs
Outdated
Show resolved
Hide resolved
beacon_node/network/src/network_beacon_processor/rpc_methods.rs
Outdated
Show resolved
Hide resolved
done! |
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at f689898 |
Issue Addressed
BeaconBlockStreamer
now runs the task of loading the blocks in a blocking thread as DB reads are slow