Reinstate tracing instrumentation on ReadOnlyDevice::encrypt
#2873
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Until #2862,
GroupSessionManager::encrypt_session_for
calledDevice::encrypt
(viaDevice::maybe_encrypt_room_key
.Device::encrypt
is a thin wrapper forReadOnlyDevice::encrypt
, but it also has aninstrument
annotation.#2862 short-cuts
Device::encrypt
and callsReadOnlyDevice::encrypt
directly: that was functionally fine but of course means that we no longer benefit from theinstrument
annotation.This PR rectifies the situation by pushing the annotation down to
ReadOnlyDevice::encrypt
. It also adds some documentation for that function, since we are using it in more places now.(Longer-term, I think we should probably aim to get rid of
Device::encrypt
altogether, but that's a refactor I don't want to take on today.)