Bug: Nodes are stuck in a specific heights when all the nodes are having same height #780
Labels
BACKWARD_COMPATIBLE
require changes that are backward compatible, no reset required
BUG
Something isn't working
HIGH_PRIORITY
needed ASAP for current sprint
Milestone
Description
This bug was found by @andy-shi88 that is caused by the recent change in deciding whether the node has finished downloading the blocks. It is because the added validation exists before the main validation.
Steps to reproduce
Expected behavior
the waiting algorithm should only be executed when the node is at height 0
The text was updated successfully, but these errors were encountered: