Open jaywink opened 4 years ago
FYI, clearing cache and reloading didn't make things better. Writing a bot message made the bot react, so it was really joined into the room. And now Riot also shows it as joined to the room after it reacted to a command.
If clearing the cache and reloading didn't help then it'll be a Synapse issue and not a Riot Web one. The timeline and currentState are both fully driven via /sync, could be a bug with Lazy Loading
or the stream ordering in synapse decided the invite comes after the join for some reason, even if the topological ordering doesn't say that.
It would be nice to work out what to report to Synapse, and then report there.
Description
Invited a bot to a room using
/invite @feneasbot:feneas.org
command.Bot joined the room. In room state Riot makes it look like the bot joined before my invite. In user list, the bot shows as still being invited and not joined.
Logs being sent: yes
Version information