matrix-org
matrix-rust-sdk
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
Performance History
Latest Results
doc(indexeddb): update changelog Signed-off-by: Michael Goldenberg <m@mgoldenberg.net>
mgoldenberg:indexeddb-event-cache-and-media-store-encrypted-tests
10 hours ago
fix(indexeddb): skip encoding event id when constructing bounds In the implementation of EventCacheStore, there are a number of places where the upper and lower bounds of an EventId are constructed. It is important to bypass hashing and encryption when constructing these bounds, otherwise the values will be modified and will no longer represent the bounds. Signed-off-by: Michael Goldenberg <m@mgoldenberg.net>
mgoldenberg:indexeddb-event-cache-and-media-store-encrypted-tests
10 hours ago
fixup! feat(room): make load_event_with_relations also load relations when falling back to the network Try loading relations from the cache before falling back to the server Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
Johennes:johannes/event-with-relations-from-remote
13 hours ago
!fixup
Hywan:fix-issue-5899
14 hours ago
fix(sdk): Better handling of redacted and redaction events in Latest Event. This patch revisits the way redacted and redaction events are handled in the Latest Event. Previously, all redacted events were considered suitable candidate. It's no longer the case. Only redaction event (`m.room.redaction`) are considered suitable candidate if and only if it targets the immediate previous event, and if and only if the previous event is itself a suitable candidate. To achieve so, the `rfind_map_event_in_memory_by` method is revisited to return the `&TimelineEvent` instead of the `OwnedEventId`. The tests have been updated accordingly.
Hywan:fix-issue-5899
14 hours ago
fix(sdk): Better handling of redacted and redaction events in Latest Event. This patch revisits the way redacted and redaction events are handled in the Latest Event. Previously, all redacted events were considered suitable candidate. It's no longer the case. Only redaction event (`m.room.redaction`) are considered suitable candidate if and only if it targets the immediate previous event, and if and only if the previous event is itself a suitable candidate. To achieve so, the `rfind_map_event_in_memory_by` method is revisited to return the `&TimelineEvent` instead of the `OwnedEventId`. The tests have been updated accordingly.
Hywan:fix-issue-5899
14 hours ago
feat(room): make load_event_with_relations also load relations when falling back to the network Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
Johennes:johannes/event-with-relations-from-remote
18 hours ago
feat[bindings]: move into specific structures the threshold and add previous values
JoFrost:main
19 hours ago
Active Branches
IndexedDB: initialize `StoreCipher` in encrypted store tests
last run
10 hours ago
#5933
CodSpeed Performance Gauge
0%
feat(room): make load_event_with_relations also load relations when falling back to the network
last run
13 hours ago
#5930
CodSpeed Performance Gauge
0%
fix(sdk): Better handling of redacted and redaction events in Latest Event
last run
14 hours ago
#5932
CodSpeed Performance Gauge
0%
© 2025 CodSpeed Technology
Home
Terms
Privacy
Docs