Always calculate state diff IDs in syncv3 #840
No reviewers
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#840
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "nex/fix-join-sync-state"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
this seemingly at least partially fixes #779 by always calculating the state diff between the sync tokens, rather than checking only if they have changed.
It appears that joins still don't come down sync immediately, but they at least now include all of the relevant state for clients. Fixes the "unnamed room" bug on many clients, and consequently fixes the bug where unsuspecting clients don't know a room is encrypted.
Would like if this could be battle tested to ensure that it does not induce additional load
Haven't had time to properly see if this actually improved anything or if it was the placebo effect, but I didn't notice any new issues arise, so I'm gonna mark this as ready to merge.
It doesn't fix the issue, but it helps it, so.
fe853c9ac8
to2bab5755dc
2bab5755dc
to52e042cb06