-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Mark sync as limited if there is a gap in the timeline #16485
Conversation
This splits thinsg into two queries, but most of the time we won't have new event backwards extremities so this shouldn't actually add an extra RTT for the majority of cases. Note this removes the check for events with no prev events, but that was part of MSC2716 work that has since been removed.
# If there is a gap then we need to only include events after | ||
# it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# If there is a gap then we need to only include events after | |
# it. | |
# If there is a gap then we need to include only events after | |
# it. |
Maybe? I'm not sure why we would do this though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we have a section of the timeline with events A, B, <gap>, X, Y, Z
we need to make sure we only send down X, Y, Z
and not A
and B
(which we currently do. If we did, then the client wouldn't try and paginate to fill in the gap.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably have a complement test?
Can someone write a bot to remind me about tests being a thing?? |
@clokep I wrote a test and it found an edge case! I've hopefully fixed it.... |
Fixes #16463