matrix-org / matrix-org/matrix-rust-sdk
timeline/event-cache: try to re-decrypt bundled events
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 500
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 106
Description
When we receive an event that contains bundled aggregations (like a replace (edit)), the bundled events could be UTDs. As a matter of fact, we should retry decrypting them later, if we can, which we don't do at the moment.
Since the timeline will incorporate bundled aggregations into a message, including an edit, this may result in an edit not showing up, if the edit event was a UTD at the time of receiving the bundled event. This should happen infrequently, though, so I deem this is low-priority.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the timeline/event-cache handling for bundled aggregations and trace how bundled events that are UTD are stored and later decrypted. Verify the retry path with a bundled edit that is initially undecryptable; done means the event can be decrypted later and the edit appears in the timeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100