Exclude old state events from sync when consumed from roomserver (#1548)
* Exclude old room events from sync when consumed from roomserver * Fix comment * Experimental hackmain
parent
3afc623098
commit
f32320a235
|
@ -189,6 +189,12 @@ func (s *OutputRoomEventConsumer) onOldRoomEvent(
|
|||
) error {
|
||||
ev := msg.Event
|
||||
|
||||
// TODO: The state key check when excluding from sync is designed
|
||||
// to stop us from lying to clients with old state, whilst still
|
||||
// allowing normal timeline events through. This is an absolute
|
||||
// hack but until we have some better strategy for dealing with
|
||||
// old events in the sync API, this should at least prevent us
|
||||
// from confusing clients into thinking they've joined/left rooms.
|
||||
pduPos, err := s.db.WriteEvent(
|
||||
ctx,
|
||||
&ev,
|
||||
|
@ -196,7 +202,7 @@ func (s *OutputRoomEventConsumer) onOldRoomEvent(
|
|||
[]string{}, // adds no state
|
||||
[]string{}, // removes no state
|
||||
nil, // no transaction
|
||||
false, // not excluded from sync
|
||||
ev.StateKey() != nil, // exclude from sync?
|
||||
)
|
||||
if err != nil {
|
||||
// panic rather than continue with an inconsistent database
|
||||
|
|
Loading…
Reference in New Issue