This failure(fail to decrypt) must not happen at all. It is debugger bug, it is not something that always will be and we should deal with it. Maybe it is not worth to make special UI. I was using this message type just for debugging.
During running may happen this event and it affects almost all living connections. After this event, all affected connections will decrypt nothing more.
Right after "the event" this percentage is small. But after that, number of bytes that failed to decrypt will be growing, because connections still alive. So in couple days it wil lbe like this.
Debugger still has this bug, but I plan to fix it properly. It will take some time, and I need to finish berkeley and yamux first
Its rather a uniqe event that indicates debugger failure, so what if we mark only connections with failed to decrypt messages?
lukasimrich
commented
2 years ago 
Links
User Interface in Figma Research in FigJam
Problem
This failure(fail to decrypt) must not happen at all. It is debugger bug, it is not something that always will be and we should deal with it. Maybe it is not worth to make special UI. I was using this message type just for debugging.
During running may happen this event and it affects almost all living connections. After this event, all affected connections will decrypt nothing more. Right after "the event" this percentage is small. But after that, number of bytes that failed to decrypt will be growing, because connections still alive. So in couple days it wil lbe like this.
Debugger still has this bug, but I plan to fix it properly. It will take some time, and I need to finish berkeley and yamux first
Its rather a uniqe event that indicates debugger failure, so what if we mark only connections with failed to decrypt messages?