Make breakpoints in Client::startSyncing() const

Check if it still crashes if we cut off network after opening

The RoomModel in libkazv should remember more than the current text-only localDraft. Should also store the state of e.g. editing or replying.

Pinned messages page: Modify the behaviour so that when the pinned messages action is triggered, the pinned messages page will replace the room page. Then, add an action in pinned messages page to return to the room page. Leave it that way until we refactor PageRow in T182 .

Some pages are left unmodified.

Move display codes and pending events into VerificationProcess

In D245#5654, @nannanko wrote:

Currently Kazv cannot remember a room is in the state of editing or replying to an event, which makes restoring a draft difficult to achieve. I think this feture should be divided into several diffs instead of being completed in one diff.

better tests and error handling

What if one party sends a bad key event? Should test that it correctly sends a cancel event of invalid_message

I don't think we want to do this. The benefits of keeping Crypto a value type isn't great. For example, it delays saving of the crypto state, which can cause problems in the case of a crash / kill of the process. A solution might be to make Crypto a dependency of the store instead.

mmore tests and error handling

Move state into VerificationProcess

more error handling

In D282#5560, @nannanko wrote:

When I enter a wrong password, then open the input box again, the old password will still be retained. Especially when I click the "show password", the input box will retain this setting. This is obviously inconsistent with the behavior of most similar software and may lead to unexpected occurrences.

Clear password before showing dialog

Add some validations

Yes you are right I think it's a change in the newer version of flatpak-cargo-generator.

doc failure is resolved in https://iron.lily-is.land/D281