-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Cannot join #html.css:matrix.org from any homeserver #14933
Comments
Internal sentry link: https://sentry.tools.element.io/organizations/element/issues/51828/activity/?project=2&query=is%3Aunresolved+send_join&statsPeriod=7d
The power levels for that room are currently: {"ban": 50, "events": {"im.vector.modular.widgets": 50, "m.room.avatar": 50, "m.room.canonical_alias": 50, "m.room.history_visibility": 100, "m.room.name": 50, "m.room.power_levels": 100, "m.room.tombstone": 0, "m.room.topic": 50}, "events_default": 0, "invite": 0, "kick": 50, "notifications": {"room": null}, "redact": 50, "state_default": 50, "users": {"@<redacted>": 100, "@<redacted>": 10}, "users_default": 0} via In particular, Indeed, synapse/synapse/push/bulk_push_rule_evaluator.py Lines 338 to 343 in 62ed877
We also don't seem to be inspecting and fixing up the |
Since this only shows up in room v10, I am guessing the room was recently created or upgraded. Can you confirm this? |
I thought room version 10 explicitly verifies the format of power-level events? I'm wondering how this got created in the first place... |
I can't, I've never been in that room. @bkil any idea? |
I have only bumped into it accidentally, so I have no information either. |
Oh, I misread. The condition is |
Description
#html.css:matrix.org seemingly cannot be joined from any homeserver (tried from e2e.zone, grin.hu, and synapse.test.progval.net)
Steps to reproduce
On either Matrix.org or another homeserver, type
/join #html.css:matrix.org
When joined from Matrix.org, the client gets this response:
{"errcode":"M_UNKNOWN","error":"Internal server error"}
When joined from another HS (Synapse), here are the logs:
Homeserver
matrix.org
Synapse Version
1.76.0rc1 (b=matrix-org-hotfixes,484db60cd6)
Installation Method
I don't know
Database
postgresql
Workers
Multiple workers
Platform
n/a
Configuration
No response
Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: