This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Auto-joining a remote autojoin room doesn't work reliably #10233
Comments
I think synapse/synapse/handlers/register.py Lines 455 to 469 in 1c8045f
We also need to handle the case where auto creating auto join is enabled but the alias is remote: synapse/synapse/handlers/register.py Lines 388 to 393 in 1c8045f
|
babolivier
added a commit
that referenced
this issue
Jun 23, 2021
If a room is remote and we don't have a user in it, always try to join it. It might fail if the room is invite-only, but we don't have a user to invite with, so at this point it's the best we can do. Fixes #10233 (at least to some extent)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Users registering on HS B can't auto-join a room on HS A that's listed in
auto_join_rooms
if they are either the 1st user on HS B or if there are no users on HS B that are in the room on HS A.Steps to reproduce
auto_join_rooms
to include the room on HS ACannot create room alias #HS-A:room-alias it does not match server domain
auto_join_rooms
as per the above fail withFailed to join new user to '#HS-A:room-alias': AssertionError()
The expectation is that
auto_join_rooms
works with any public room local or federated.Version information
The text was updated successfully, but these errors were encountered: