-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Enrich the sync log on handling the block request #11747
Conversation
Add more info to the log to help debug the issue like https://github.com/paritytech/substrate/issues/11732.
|
||
debug!( | ||
target: LOG_TARGET, | ||
"Sending result of block request from {peer} starting at `{from_block_id:?}`: \ |
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 should be put into the if
branch? Because we don't send any block response in the None
case? We can instead add a second logging that says that we don't send any response.
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.
Hmm, actually we still send a response in terms of the OutgoingResponse
below, which contains a result Err(())
in the case of None
. blocks
will be displayed as Some(100)
or None
which indicates we send 100 blocks or we don't send back any blocks, should be clear enough for the diagnostic purpose IMO.
bot merge |
Waiting for commit status. |
Merge cancelled due to error. Error: Statuses failed for 32e36c9 |
Add more info to the log to help debug the issue like https://github.com/paritytech/substrate/issues/11732. Co-authored-by: Bastian Köcher <info@kchr.de>
Add more info to the log to help debug the issue like https://github.com/paritytech/substrate/issues/11732. Co-authored-by: Bastian Köcher <info@kchr.de>
Add more info to the sync log to help debug the issue like
paritytech/polkadot-sdk#531.
cc @arkpar