-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Inviting a user to a group twice breaks the group #2633
Comments
I found this line in the homeserver.log, which makes the issue seem pretty self-explanatory:
|
This just happened to me. A user joined a group but got an error (don't have an exact error msg, "Couldn't join group" or something like that), so I invited them again. Now the group can't be listed anymore in Riot. Checking the database, there are two entries for this user in group_users, and also in attestations_remote. There is no unique index on group_users or the attestation tables, is that intentional? Either way, something is definitely up here.. The user in this case is on matrix.org (do you have the duplicate entry too, now?), the group is on stratum0.org. |
@Valodim I had to fix this by manually deleting the duplicate rows in the database |
Got hit with this bug a couple of time now. 😞 |
I have also got hit with this twice in the last two days. The last person to trigger it claims that he only pressed the join community button once! |
This appears to be the TODO regarding this issue. |
This does appear to have been made significantly worse by the introduction of publicly joinable groups as that TODO will not stop someone joining a public group twice. I wonder if this could just be fixed by having SQL enforce uniqueness rather than doing it in the synapse code? |
It seems that this issue has started appearing again. In particular, we have seen it happening on +polynomial-supporters:matrix.org Wherever the problem occurs we see |
fwiw I saw this when the user tried to accept their second invite, not when the invite was issued. |
Synapse is currently known (matrix-org/synapse#2633) to return 500 errors for requests to `/groups/$groupId/users` when a user has multiple invites to the group. If you are affected by this issue, Riot will display a community invite when you select it for a few seconds until it receives this 500 error, but then it will replace the invite view with a "Failed to load <group>" message. By ignoring this error response in Riot for now, it is possible to view and accept the invite. Signed-off-by: J. Ryan Stinnett <jryans@gmail.com>
Synapse is currently known (matrix-org/synapse#2633) to return 500 errors for requests to `/groups/$groupId/users` when a user has multiple invites to the group. If you are affected by this issue, Riot will display a community invite when you select it for a few seconds until it receives this 500 error, but then it will replace the invite view with a "Failed to load <group>" message. By ignoring this error response in Riot for now, it is possible to view and accept the invite. Fixes element-hq/element-web#7727. Signed-off-by: J. Ryan Stinnett <jryans@gmail.com>
Communities/groups are being removed, see #11584. |
Description
After the same user joined a group twice, all requests for group information now return a 500 Internal Server Error
Steps to reproduce
/groups/:group_id/admin/users/invite/:user_id
API)I just realized I had a broken log config for this HS, so I have no homeserver.log to look in. I can fix that and then look at the logs though, if that's necessary
Version information
The text was updated successfully, but these errors were encountered: