Adding canStartOwnDataConsensus to avoid error during the data-l1 consensus and halting the streaming

Constellation-Labs / tessellation

Monadic execution contexts for topology organization

Apache License 2.0

49 stars 28 forks source link

Closed IPadawans closed 3 months ago

IPadawans commented 3 months ago

We had a bug that the data-l1 consensus was being stopped when the lastGlobalSnapshot wasn't present. This error was halting the streaming and blocking the node from starting the own consensus
I've followed the pattern of the currency layer and added a validation to the data consensus before trying to start the own consensus

It was working as expected, as the image below illustrates