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
I'm not quite sure if this is a real bug or a problem with synapse, but I just want to rise awareness for this, maybe something can be done.
We stumbled upon a bug yesterday where 1:1 messages after synapse upgrade could be sent to one server but not the other way around (see matrix-org/synapse#7099)
The "problem" with riot is that the users did not get any indication that the messages could not be delivered. I'm not sure if riot actually receives any information about this from the homeserver, in this particular case.
Versions involved:
Hard to figure out afterwards, there have been multiple versions of riot web (and some riotX) involved, but at least one instance of riot web 1.5.12. Also multiple OS from Windows to Linux and Browser from Firefox to Chrome in different versions have been used.
The text was updated successfully, but these errors were encountered:
I'm not sure if riot actually receives any information about this from the homeserver, in this particular case.
Riot only gets to know if the message was successfully persisted into the room, as Matrix is eventually consistent it is actually considered acceptable that messages may not arrive for a while.
* Update base card styling to match Compound
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Update screenshot
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
---------
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
Description
I'm not quite sure if this is a real bug or a problem with synapse, but I just want to rise awareness for this, maybe something can be done.
We stumbled upon a bug yesterday where 1:1 messages after synapse upgrade could be sent to one server but not the other way around (see matrix-org/synapse#7099)
The "problem" with riot is that the users did not get any indication that the messages could not be delivered. I'm not sure if riot actually receives any information about this from the homeserver, in this particular case.
Versions involved:
Hard to figure out afterwards, there have been multiple versions of riot web (and some riotX) involved, but at least one instance of riot web 1.5.12. Also multiple OS from Windows to Linux and Browser from Firefox to Chrome in different versions have been used.
The text was updated successfully, but these errors were encountered: