-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Rejected event made it into current_state_events
, leading to errors such as 404: Could not find event
#6867
Comments
Hmm, looks like you're either missing the ACL event or its been reject and somehow its ended up in current state? Might be worth seeing if leaving/rejoining fixes? |
That event is:
Which is also in:
|
Ruh roh |
@Half-Shot: is that event the one in current_state_events for that room_id/event_type? |
@richvdh Yup:
|
well boo. An event that fails auth shouldn't make it into current_state_events afaik. I don't suppose you have logs going back as far as Jan 23rd (when that event landed)? |
The logs have rotated many times since then :( |
current_state_events
, leading to errors such as 404: Could not find event
we're going to park this until we have logs to demonstrate it happening |
I have a feeling that this sort of thing could have happened pre-synapse 1.6.0 due to #6289. 1.6.0 was released on 2019/11/26; I wonder if @Half-Shot was still running an older version on 23rd Jan. Interestingly it turns out @uhoreg has the same problem with the same room. |
Workaround was to leave the room and re-join. |
#10589 reports a similar problem with another event ( |
We're hoping this is fixed going forward, so I'm going to close this. |
Seems like this can still happen. |
a |
I'm not seeing any inbound federation to #irc:matrix.org (!BAXLHOFjvDKUeLafmO:matrix.org), and my logs are full of:
The text was updated successfully, but these errors were encountered: