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 has been archived by the owner on Apr 26, 2024. It is now read-only.
However, it appears we do not persist those events to the state group, which means that the room state stays out of sync, and leads to further rejections down the line. (For instance, if the new event was a join, and the invite_rules was missing from the state group, then the join will later get rejected during conflict resolution).
The real question is why the auth events are missing in the state group (which is probably due to #1935), but given we have this self-healing mechanism, it would be nice if it worked.
The text was updated successfully, but these errors were encountered:
When we receive an event whose auth chain includes events which are missing from the state group at the relevant point on the DAG, we include those missing events when authing the new event. (see https://github.com/matrix-org/synapse/blob/09eb08f/synapse/handlers/federation.py#L1510).
However, it appears we do not persist those events to the state group, which means that the room state stays out of sync, and leads to further rejections down the line. (For instance, if the new event was a join, and the
invite_rules
was missing from the state group, then the join will later get rejected during conflict resolution).The real question is why the auth events are missing in the state group (which is probably due to #1935), but given we have this self-healing mechanism, it would be nice if it worked.
The text was updated successfully, but these errors were encountered: