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
{{ message }}
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
since I cannot find another path for "Unknown room" to do with syncs.
EDIT2:
synapse=# SELECT type, state_key, event_id FROM current_state_events
synapse-# WHERE room_id = '!YztxsnzcdfOllJOvZA:jcg.re';
type | state_key | event_id
---------------+-------------------------+----------------------------------
m.room.member | @Half-Shot:half-shot.uk | $1537608760248JGTdh:half-shot.uk
my current_state_events table is miserable though.
EDIT3: Fixed by logging out and in, and doing an initial sync. I suspect I wasn't actually in the room and there was no state for it, however the sync I was using figured I was in the room hence the confusion. Not sure what there is to fix here. Perhaps we should drop any rooms that have incorrect state in the incremental syncs.
Description
Not sure why it has started doing it, but I am seeing
{"errcode":"M_NOT_FOUND","error":"Unknown room"}errors when trying to do an incremental sync.Version information
EDIT1:
It's very likely
synapse/synapse/storage/state.py
Line 434 in 678ad15
EDIT2:
my
current_state_eventstable is miserable though.EDIT3: Fixed by logging out and in, and doing an initial sync. I suspect I wasn't actually in the room and there was no state for it, however the sync I was using figured I was in the room hence the confusion. Not sure what there is to fix here. Perhaps we should drop any rooms that have incorrect state in the incremental syncs.