Skip to content
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

fix: Remove support for MSC3575 #4531

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Hywan
Copy link
Member

@Hywan Hywan commented Jan 14, 2025

MSC3575 is the “first” and “old” version of sliding sync, implemented by the sliding sync proxy and probably other homeservers. MSC4186 is the “next” and “new” version of sliding sync, being implemented inside Synapse and probably other homeservers.

The Matrix Rust SDK was supporting both versions, aiming at giving time to homeservers to transition from the experimental MSC3575 to the stable, production ready MSC4186.

It is time to say good bye to MSC3575. This is what the first patch does.

This patch also needs to update ruma (to include ruma/ruma#1995). Updating ruma involves a bit of breaking changes, it's addressed in a standalone second patch.

@Hywan Hywan force-pushed the fix-remove-msc3575 branch from 013c7d7 to c8a3d71 Compare January 14, 2025 15:12
Copy link

codecov bot commented Jan 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.69%. Comparing base (8a76587) to head (a1a3d95).
Report is 16 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4531      +/-   ##
==========================================
- Coverage   85.70%   85.69%   -0.02%     
==========================================
  Files         292      292              
  Lines       33406    33291     -115     
==========================================
- Hits        28632    28530     -102     
+ Misses       4774     4761      -13     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@bnjbvr bnjbvr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exciting! I'd really like the Ruma update to happen separately, because it involves non-trivial changes related to reply fallbacks that I'd like to review without other changes, pretty please 🥺 🙏

crates/matrix-sdk-base/src/read_receipts.rs Outdated Show resolved Hide resolved
crates/matrix-sdk-base/src/sliding_sync/http.rs Outdated Show resolved Hide resolved
crates/matrix-sdk/src/client/futures.rs Show resolved Hide resolved
crates/matrix-sdk/src/event_cache/room/mod.rs Outdated Show resolved Hide resolved
@Hywan
Copy link
Member Author

Hywan commented Jan 14, 2025

Yup, sure, ruma update has been extracted in #4532.

@Hywan Hywan force-pushed the fix-remove-msc3575 branch 2 times, most recently from 4453a79 to 04ee9ee Compare January 20, 2025 14:22
Hywan added 2 commits February 5, 2025 15:17
This patch inlines `sliding_sync::http` inside `sliding_sync`. Then, the
`sliding_sync/mod.rs` file is renamed to `sliding_sync.rs`.
@Hywan Hywan force-pushed the fix-remove-msc3575 branch from 04ee9ee to 5f4e046 Compare February 5, 2025 14:18
@Hywan Hywan requested a review from bnjbvr February 5, 2025 14:27
@Hywan Hywan force-pushed the fix-remove-msc3575 branch from 07f4176 to b7ba81e Compare February 5, 2025 19:13
This patch removes the `pub use ruma::api::client::sync::sync_events::v5
as http` re-export in `matrix_sdk_base::sliding_sync`.
@Hywan Hywan force-pushed the fix-remove-msc3575 branch from b7ba81e to a1a3d95 Compare February 5, 2025 19:19
@Hywan Hywan marked this pull request as ready for review February 5, 2025 19:33
@Hywan Hywan requested a review from a team as a code owner February 5, 2025 19:33
Copy link
Member

@bnjbvr bnjbvr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yay 🔥 🔥 🔥

(I'll trust you'll fix the Complement Crypto API mismatch before landing 🙏)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants