This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Yet another case of state reset in State Resolution v2 #16629
Labels
A-State-Resolution
O-Occasional
Affects or can be seen by some users regularly or most users rarely
S-Major
Major functionality / product severely impaired, no satisfactory workaround.
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Description
I have encountered yet another room state reset.
I suspect that the reset of
m.room.join_rules
was the root cause of the 51m.room.member
resets, as the latter would now be rejected events. There is no obvious explanation for them.room.join_rules
reset.No state events were sent or redacted in the time immediately preceding the state reset. The last state event before the reset was sent approximately 2 hours prior.
Steps to reproduce
Homeserver
arcticfoxes.net
Synapse Version
1.96.0rc1
Installation Method
Debian packages from packages.matrix.org
Database
PostgreSQL 15.4, single server, not ported, restored a very long time ago
Workers
Single process
Platform
Configuration
Relevant log output
SELECT * FROM current_state_delta_stream WHERE room_id='!frWBWOPyriepLexnsA:arcticfoxes.net' AND stream_id=25794806;
Anything else that would be useful to know?
In addition to arcticfoxes.net documented above, this state reset was confirmed via the C‑S API on matrix.org (Synapse 1.96.0rc1) and a third server (Synapse 1.95.1). I do not know the exact details of their deployments.
The text was updated successfully, but these errors were encountered: