Some rooms are erroneously going missing #824
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#824
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While trying to call /forget on some rooms, a few of them reported that the user forgetting the rooms was never in them.
Upon further investigation, it looks like the server doesn't know about these rooms at all.
It turns out, the
roomid_shortroomid
for the relevant rooms is missing - the state and whatnot appears to still be there.Symptoms look like
Forgetting room !room:example: Error: 400 {"errcode":"M_UNKNOWN","error":"M_UNKNOWN: No membership event was found, room was never joined"}
andMissing state for "!room:example": M_NOT_FOUND: Not found in database
Possibly related to this could be that the rooms I have managed to investigate lack relevant membership events for the given users, even though they're in the
/sync[rooms.leave]
payload. It looks to me like affected rooms have state reset beyond use (i.e. bricked), however I haven't been able to check many rooms. needs investigation.