At the moment, investigating messages is incredibly tedious due to the high volatility in storage. We will need a better way to investigate messages after they've been removed from the consensus queue.
This PR logs all messages as they're removed from the queue, so we can see what's happening through the logs.
Change consensus keeper cdc from BinaryCodec to Codec. The Codec interface embeds BinaryCodec as well, so we don't lose functionality. However, Codec also adds JSONCodec.
Create MessageWithSignatures from QueuedSignedMessageI.
Marshal messages with cdc.MarshalJSON as we remove them from the queues. We get the output formatted the same as in the CLI commands.
Testing completed
[x] test coverage exists or has been added/updated
[x] tested in a private testnet
Breaking changes
[x] I have checked my code for breaking changes
[x] If there are breaking changes, there is a supporting migration.
Related Github tickets
Background
At the moment, investigating messages is incredibly tedious due to the high volatility in storage. We will need a better way to investigate messages after they've been removed from the consensus queue. This PR logs all messages as they're removed from the queue, so we can see what's happening through the logs.
cdcfromBinaryCodectoCodec. TheCodecinterface embedsBinaryCodecas well, so we don't lose functionality. However,Codecalso addsJSONCodec.MessageWithSignaturesfromQueuedSignedMessageI.cdc.MarshalJSONas we remove them from the queues. We get the output formatted the same as in the CLI commands.Testing completed
Breaking changes