Fix a bug in rollup node
- Jun 16, 2022
-
-
Verified4fed21bf
-
This is not totally related but this large output makes the CI fail. Signed-off-by: Yann Regis-Gianas <yann@nomadic-labs.com>
Verifieddfded118 -
Signed-off-by: Yann Regis-Gianas <yann@nomadic-labs.com>
Verified05fec0d1 -
Signed-off-by: Yann Regis-Gianas <yann@nomadic-labs.com>
Verifiedc0803ef4 -
To be robust to interruption in the middle of processes, we accept to redo some work when we restart the node. Hence, it is fine to insert twice the same value for a Signed-off-by: Yann Regis-Gianas <yann@nomadic-labs.com>
Verified78ba8bbe -
When the queue of heads to be processed is not empty and the rollup node is terminated, the heads in the queue are never processed when the rollup node is restarted. This commit fixes the issue by remembering the processed heads and to include unprocessed heads in the intermediate heads to catch up with the mainnet heads. Signed-off-by: Yann Regis-Gianas <yann@nomadic-labs.com>
Verifiedceaf77c3
-