You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@karknu found a misbehavior with a small docker-composetestnet, and asked Consensus to dig in. If the node had been reporting its GSM state with some frequency automatically, then it would have taken us 5 minutes to create our feedback instead of a few hours (since we struggled to understand the docker-compose configuration mechanisms).
This Issue is to add two tracers to the GSM:
trace the initial GSM state on start up
every 10s or so, trace the current GSM state
These seem small enough to be in the node enabled by default --- at least in ConsensusNode: GenesisMode.
The text was updated successfully, but these errors were encountered:
@karknu found a misbehavior with a small
docker-compose
testnet
, and asked Consensus to dig in. If the node had been reporting its GSM state with some frequency automatically, then it would have taken us 5 minutes to create our feedback instead of a few hours (since we struggled to understand thedocker-compose
configuration mechanisms).This Issue is to add two tracers to the GSM:
These seem small enough to be in the node enabled by default --- at least in
ConsensusNode: GenesisMode
.The text was updated successfully, but these errors were encountered: