Sean Quah
Sean Quah
After discussions with @erikjohnston, we've decided to deprioritize this edge case, since there are other known bugs in device list tracking when servers disagree about the members in a room.
Is this still happening on recent releases of Synapse?
On SQLite in monolith mode, the test fails reliably if modified so that Bob's join appears in an initial sync. Bob's presence is offline(!) and it's only sent during incremental...
We appear to only bump presence when Bob sends a regular message. https://github.com/matrix-org/synapse/blob/86c5a710d8b4212f8a8a668d7d4a79c0bb371508/synapse/handlers/message.py#L1918-L1921 That condition has been around since https://github.com/matrix-org/synapse/commit/f70e622d59e7b97c539ee03ffc02315b4d626b00 from 2014. However, https://github.com/matrix-org/synapse/commit/b31ec214a5c2bd674814b2d052200963c5e5cbd7 modified the bump to only transition...
After #10598, passing `"password": null` no longer results in an "Invalid password" error. Omitting the "password" field still results in a "Must provide a password to re-activate an account" error,...
@marcel375 What part of login does the user get stuck on? Can you upload logs spanning the login attempt?
From the sounds of it, Synapse thinks the account is already re-activated. We're going to have to figure out which part of the login is stuck or failing in order...
(Moved a series of comments into their own issue: #12456)
PRs the fix the docs welcome.
https://github.com/matrix-org/synapse/issues/14056 https://github.com/matrix-org/synapse/actions/runs/3188210616