Add reason of NoRequestNeeded to lookup sync#6317
Conversation
d4581c8 to
c0fa672
Compare
jimmygchen
left a comment
There was a problem hiding this comment.
Nice, I think this will help with debugging 👍
|
@mergify queue |
🛑 The pull request has been removed from the queue
|
# Conflicts: # beacon_node/network/src/sync/network_context.rs
|
@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 60157ad |
* Add reason of NoRequestNeeded to lookup sync * Merge branch 'unstable' into peerdas-reason # Conflicts: # beacon_node/network/src/sync/network_context.rs
* Add reason of NoRequestNeeded to lookup sync * Merge branch 'unstable' into peerdas-reason # Conflicts: # beacon_node/network/src/sync/network_context.rs
Issue Addressed
Porting improvement from
Proposed Changes
Now there are more reasons why a lookup request will be
NoRequestNeeded. To debug stuck sync lookup it's important to know why sync would consider the request unnecessary.