-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Stop backpaginating when events not visible #4699
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #4699 +/- ##
==========================================
- Coverage 75.09% 74.4% -0.69%
==========================================
Files 340 340
Lines 34923 35795 +872
Branches 5723 5982 +259
==========================================
+ Hits 26225 26635 +410
- Misses 7088 7518 +430
- Partials 1610 1642 +32 |
8da569d
to
7356052
Compare
When filtering events to send to server we check more than just history visibility. However when deciding whether to backfill or not we only care about the history visibility.
7356052
to
d1523ae
Compare
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.
are we not likely to end up doing the filter_events_for server thing (which is quite expensive) repeatedly, every time anyone asks for some backfill? Should we cache the results of this somehow? (possibly in a separate PR?)
generally seems sane to me.
# TODO: If we do do a backfill the we should filter the extremities to | ||
# only include those that point to visible portions of history. | ||
# | ||
# TODO: Correctly handle the case where we are allowed to see the |
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.
how would we do this? is it a thing we are ever likely to be able to do? if not, a TODO is inappropriate
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.
It should be possible, I've updated the comment with roughly what's needed.
No description provided.