-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
A user joined a v3 room and a lot of users were left. #4980
Comments
Some addtional detail from my POV: for many HSs I can't see their events (presumably because I'm not being sent them because they've rejected my join; however this does not square with the fact that this happens with messages from |
I should note that the join event mentioned ( |
We seem to be failing to find time to investigate this :/ |
This certainly doesn't sound like a conventional "state reset" (which affects all servers equally); rather it's a different problem which we have no reason to believe would be affected by the change in state resolution algorithm.
Do we know why the member event was rejected? Any logs from any affected servers?
"Not in the room" according to what metric? |
this just doesn't feel like a thing that we're ever going to investigate. |
This is an ongoing bug report because there are a few moving parts and I am not sure of all the details yet, but will try to explain as best as I can.
#watercooler:half-shot.uk (!gdRMqOrTFdOCYHNwOo:half-shot.uk) is a v3 room that has been upgraded several times before.
$gzD61zfxtq5zoyrFLiY2ILt0SzUEwGJu90c229pKHww
and a lot of servers reject the event. My server (half-shot.uk
) did not.The text was updated successfully, but these errors were encountered: