Joins and inbound federated invites are not received on /sync

[ara4n]

No description provided.

[ara4n]

doing an initial sync by flushing cache reveals them however.

[richvdh]

presumably related to #4422

[richvdh]

to be clear, I'm not actively investigating this until I get more reports of it

[ara4n]

@erikjohnston saw a variant of this twice with me this evening - one on jki.re and one on kde.modular.im. In both instances we were trying to join an IRC portal room: the /join went through fairly rapidly (you could see the user join on the IRC side, and we traced the /join in the logs), and in both instances it looks like the room state never came down the /sync so Riot/Web never believed the room had been joined and sat there spinning. The only solution was to flush cache. Meanwhile, Riot/Android correctly saw the room as having been joined.

[richvdh]

@erikjohnston saw a variant of this twice with me this evening - one on jki.re and one on kde.modular.im.

@erikjohnston denies having an account on kde.modular.im, so this is misleading at best...

[ara4n]

sorry. I think @erikjohnston was trying to join ##c++ from jki.re, which failed. He then saw me as @matthew:kde.org try to join, uh, somewhere on freenode and have it also fail - sorry, i've already forgotten the room.

But assuming jki.re still has logs for the ##c++ thing it should be debuggable?

[richvdh]

This is superficially similar to #4422; however the bug that we found there could only affect worker-mode synapses, and given that this has been seen (iirc) on monolith deployments, there is probably still another bug out there somewhere.

[richvdh]

I think I'm going to close this until we have more reports of it happening that we can investigate.