-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
state resets still happen in v2 rooms #8629
Comments
Just to clarify, that means that it still happens in v2+ (3...9) versions right? |
Yes, since the state resolution algorithm hasn't been changed since room version 2 |
Hello! I'm experiencing this bug as well. Every month I'm being added to #dendrite room (which is a v1 room, I suppose) and I can't even leave this room because nothing happens when I click "Leave". |
Hey there, |
I was under the impression that state res v2 was studied and deemed sound. https://matrix.org/blog/2020/06/16/matrix-decomposition-an-independent-academic-analysis-of-matrix-state-resolution . Did the research group finish work on a formal proof? |
There's a large project within the core team currently working through a new formal expression of state res v2 to try to characterise the remaining issues. Given the risk of discovering security issues, it's being treated as an internal security project (juggled alongside our other security work). There's been some progress in identifying the root cause here though; will update as soon we can. |
Hi @jae1911. I would like to look into the details here. Could you share
|
Hey there, sure!
Ping @DMRobertson ; state reset occurred in the night of the 2022/08/03; here is the
|
@jae1911 I assume this is from the perspective of Are you able to run sql queries on the Synapse database hosting |
Thanks for getting in touch @jae1911. From the queries we ran, we saw that from the point of view of
The first two bullets are identical to what I see on Therefore, I don't think this is an example of a server-side state reset; rather, I think this is an instance of matrix-org/matrix-spec#1209 (or something like it) where clients can have their view of state differ from that of the server. Debugging that problem will be fiddly and should hopefully be avoided by using sliding sync rather than that current sync API. With that said, please do let me know if you see another instance of state that appears to have reset unexpectedly. I will edit the description of this to include the relevant sql queries for any future reports. |
This comment was marked as resolved.
This comment was marked as resolved.
I don't see the reset in matrix.org's database. Are you able to run the SQL queries in the description? |
I am not a server admin anywhere |
This Message was deleted but can still be seen on matrix.org
asra.gr user:
Occouring approximatly 8:58 CEST Message was send after the user was banned. €dit: |
Sounds like there was some delay in the redaction event |
I had created |
Thanks for the report. I took at look at this today. It seems that I could see that two users' power levels dropped from 50 to either NULL or 0. However, three other users' power levels never dropped from 50, and the room creator's power level never dropped from 100. (I've been somewhat vague here: the room is private, and I don't want to publish any room, event or user IDs.) Of note: the two users who saw a drop were both appservice-managed users---in this case, users managed by an IRC bridge to If you're using element web, I'd recommend clearing its caches on the off-chance there is a client-side problem reporting an older set of power levels for some reason.
This doesn't match what I see in the matrix.org database (five users currently at power level 50, the room creator at power level 100). |
Thanks, this actually adds up with what I remember happening. We had a different room in the past, and at some point several months ago, the IRC bridge was acting up and required bridge admin intervention. When trying to fix this, I moved us all to this room that had been created by that specific creator (staying intentionally vague here, but I'm sure you will understand exactly what I mean). Apparently in the process our power levels became Moderators instead, and I never noticed until now because that happens to give me enough privileges to manage a low-traffic room with just friends. I guess it can stay like this then, people can get moderator status by opping themselves on the IRC side, where I can manage ChanServ. Thanks for your investigation! |
We at Can this situation be confirmed somehow and that room upgrade is absolutely necessary or is knowledge of it at all helpful? I understand that DAG splits are also tracked in this issue. |
We'd need more details (see also the top comment, which I edited some months back with some suggestions). Whose avatar is being split? Which servers see it differently; ideally, which event ID do they report as being current? |
I don't know how to see current event ID. I have no access to any database personally. I am going by assumption that it's better that issues like this are reported rather than letting them happen silently and migrating to protocols where they don't happen. DAG split was claimed in event https://matrix.to/#/%23fluffychat%3Amatrix.org/%24DN3Au8zP9FMwDXULg_ZJZmXkw5BcKVDCL-BHx3-ARvM?via=pikaviestin.fi&via=matrix.org&via=the-apothecary.club&via=envs.net |
I have documented a new case of state reset at #15987 (comment). |
I have documented a new case of state reset at #16629. |
I just upgraded
#synapse:matrix.org
because I got fed up of losing my ops bit. It was a v4 room.EDIT 2022-08-03 by @DMRobertson: if you suspect you have seen a state reset, please provide:
room_id
of the room with the resettype
andstate_key
that suffered a resetTo confirm if this really is a server-side state reset (rather than e.g. matrix-org/matrix-spec#1209), server administrators can run the following queries.
The last row in the
event_id
columns from these two queries should match. It represents the event which currently describes the relevant piece of state from your server's point of view.The text was updated successfully, but these errors were encountered: