piersy
piersy
## Description We currently have 2 variables for tracking the round of the consensus protocol, but if you look at where they are used you can see that they could...
## Description Whilst investigating a recent [forno incident ](https://www.notion.so/clabsco/Blockchain-heavy-load-e3d189f092fd4cfaabbea803a3763875#a63e722ed2f0438580247fde729e7b15) I was making use of the forno dashboard in graphana and there were some things that were missing that would be...
## Description When investigating incidents it would be very useful to have a tool that would allow you to easily query data from the chain. For example * Show the...
E.G: * get these metrics for this group of clusters * make a dashboard showing X * get the logs of transaction X * redeploy a cluster in Forno
Check access to systems, check status of running systems ... etc
## Description Once we have a pseudocode specification for our current consensus protocol #1690 , we can generate a state machine diagram from it.
The (code coverage/test loc) metric is a proxy for how easy it is to test your code, this is going to be a useful metric to measure refactoring progress in...
## Description #1622 fixes a regression introduced in #1592 we don't have any automated tests to check that future changes are not breaking data formats. ### Expected Output Some automated...
When different validators commit in different rounds, all but one round will have signatures dropped
The istanbul consensus algorithm allows blocks to be committed in different rounds although it enforces that if a block was committed in a previous round, then only the same block...
This is a dashboard to view the health of the chain as opposed to the health of Forno.