You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with from = 0, to=10. This ultimately returns a range of (2, 10), because our join event has NID 2. But the create event has NID 1, and so is not loaded from the database.
The text was updated successfully, but these errors were encountered:
I was surprised by this, but it may not be a bug given that clients can explicitly request the m.room.create state.
Integration test to reproduce:
which fails with
I think this is because we load timelines here
sliding-sync/sync3/handler/connstate.go
Line 567 in ae9777d
where anchorloadPos is 0. That calls
sliding-sync/sync3/caches/user.go
Line 318 in db7e94d
with loadPos 0, maxTimelineEvents 10. Next we call
sliding-sync/state/storage.go
Line 698 in c3dfd66
with
to
= 10. The next level issliding-sync/state/storage.go
Line 772 in c3dfd66
with from = 0, to=10. This ultimately returns a range of (2, 10), because our join event has NID 2. But the create event has NID 1, and so is not loaded from the database.
The text was updated successfully, but these errors were encountered: