threads: Bulk process thread subscription updates from sync and companion enpoint#5848
Conversation
2417153 to
cfcfa42
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #5848 +/- ##
========================================
Coverage 88.54% 88.55%
========================================
Files 363 363
Lines 103703 103885 +182
Branches 103703 103885 +182
========================================
+ Hits 91821 91992 +171
- Misses 7517 7519 +2
- Partials 4365 4374 +9 ☔ View full report in Codecov by Sentry. |
CodSpeed Performance ReportMerging #5848 will not alter performanceComparing Summary
|
cfcfa42 to
9a19738
Compare
|
Thanks! It looks like a solid contribution, thank you. However, I wonder if you could add a bit of context and to explain what you're doing, and why, please? |
9a19738 to
07a7e45
Compare
The sliding sync and back-pagination endpoints provide thread subscription updates in batches, but currently the SDK stores/updates them one by one. (MSC4308) The first commit adds the Most of the Switching to a bulk api was suggested in this comment. |
|
Can you please fix the broken test? |
It passes locally and in the first CI run all tests passed. It does contain thread_subscriptions in the name, but i didn't edit this test or logic around it :D I don't think i can re-run the pipeline. Can you re-run it or should i do a rebase to trigger it? |
|
For a reason I ignore, I can't re-run the jobs… Can you push an empty commit please, or rebase on top of |
…ethod for bulk upsert
|
Sure, i'll rebase it |
07a7e45 to
d4d5d6e
Compare
|
I think it's worth considering the |
|
Thank you for reviewing! Yes, the old method can be removed. Could you please assign the new issue to me? |
|
I can't assign it to you, but feel free to comment you're working on it! |
| - Add `StateStore::upsert_thread_subscriptions()` method for bulk upserts. | ||
| ([#5848](https://github.com/matrix-org/matrix-rust-sdk/pull/5848)) |
There was a problem hiding this comment.
In our changelogs, the most recent changes go at the top. Also, this did not land in the 0.16.0 release, so it is in completely the wrong place.
@Hywan as reviewer, please can you take responsibility for fixing up the changelogs?
Fixes #5610
Signed-off-by: Razvan razvanvp@gmail.com