-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crypto: Log details about olm session after encryption/decryption #3242
Conversation
self.last_use_time = SecondsSinceUnixEpoch::now(); | ||
debug!(?session, "Successfully encrypted an event"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm deliberately moving this field from the span, to the individual event. Firstly, it's quite a lot of data and, if there were more than one event in this span, we wouldn't want to log it on every event. More importantly, it's important that we capture the state of the session after the encryption happens (we want to know if it's stepped the DH ratchet, etc.) Given that the state of the session
changes over the lifetime of the span, it feels inappropriate to attach it to the span.
0ab64b8
to
abf5eac
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3242 +/- ##
=======================================
Coverage 83.73% 83.74%
=======================================
Files 238 238
Lines 24567 24565 -2
=======================================
- Hits 20572 20571 -1
+ Misses 3995 3994 -1 ☔ View full report in Codecov by Sentry. |
Don't you want to bump the vodozemac dep as well? |
Well I do, but this can land independently, so I thought I'd put it up for review while we're still dealing with vodozemac PRs. |
Together with matrix-org/vodozemac#133, this produces output like:
and: