-
-
Notifications
You must be signed in to change notification settings - Fork 660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Number of room members sometimes incorrect #2514
Comments
When this happens, does the actual member list also have lots of missing users, or is there an obvious disconnect between the users in the member list and the membership count? |
I'm pretty sure it's only the count that's wrong and the member list is right, certainly that's the case for the smaller rooms where I can count the users myself and get ~20 whereas dendrite counts 0 or 1. The room with 0 is still listed in spaces summaries (despite #2504 (comment) - rooms are reliably not listed in spaces summaries for me if there's no users from the current homeserver in that room), so dendrite does consider that room to have members for that code path. |
Regression test added in matrix-org/complement#551 Should fix #2514?
Hopefully this is fixed now, if not, feel free to reopen. |
I havn't seen the 0 users bug again (so far), but our main room still shows too many users (+12) and #dendrite:matrix.org and #dendrite-dev:matrix.org both show 2 users less on dendrite than on matrix.org (this is much closer than it used to be). |
I was able to fix all remaining user count discrepancies with the downloadState admin API feature. |
Background information
go version
: 1.17.10Description
Steps to reproduce
I don't know how to reproduce reliably. Some rooms have the correct user number, some are out by 1 or 2, others by a lot.
#dendrite:matrix.org often differs by > 100.
Recently when a new (dendrite) user joined 2 existing rooms, the user count suddenly dropped. One room now is shown with 0 people, the other has 1, but both rooms still have about 20 people in them.
The text was updated successfully, but these errors were encountered: