Track the number of ratchet advances in the Olm Session, and include it in the debug output.

[richvdh]

In order to help understand Olm decryption errors, let's keep track of the number of DH ratchet clicks, and log them as part of the debug output.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 81.48148% with 5 lines in your changes are missing coverage. Please review.

Project coverage is 84.65%. Comparing base (7a1887f) to head (5599cef).
Report is 1 commits behind head on main.

Files	Patch %	Lines
src/olm/session/double_ratchet.rs	81.81%	4 Missing ⚠️
src/olm/session/receiver_chain.rs	50.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #134      +/-   ##
==========================================
- Coverage   84.72%   84.65%   -0.08%     
==========================================
  Files          32       32              
  Lines        1768     1786      +18     
==========================================
+ Hits         1498     1512      +14     
- Misses        270      274       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[poljar]

Looks good, I left some nits and I'm going to require tests for this one.

[poljar]

I'm afraid I need to inform you that vodozemac never abandoned git-cliff for changelog entries. So this belongs in a commit message.

[richvdh]

ah, right. Presumably putting it in the subject line of the PR, and then squash-merging the PR, will do the right sort of thing?

[poljar]

As long as it's a conventional commit it will be picked up, since you historically complained that commit messages don't make great changelog entries you can put the conventional commit into a merge commit.

The merge commit message is anyways useless so it's a good opportunity to repurpose it for a better cause.

In the future I'd like to make it possible so you can have a special tag in merge commits which will mark the start of the changelog entry, similar to how the Signoff is treated specially in commit messages.

[richvdh]

ok, well, I've removed this for now.

[richvdh]

@poljar: have added some tests. Let me know what you think. Happy to add more if you have suggestions.

[poljar]

Looks good, thanks for the tests.