-
Notifications
You must be signed in to change notification settings - Fork 6
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
Accepting invites from federation fails #12
Comments
Same here. It seems that the module doesn't support federation |
Any clues on the cause of that or possible workarounds? |
I'm getting the same error here. Any updates on this? |
Taking a look at this I think the issue is caused by a race condition where the To figure this out I used the demo script to run two servers in a private federation, added the module to one of them and added a bunch of logging. |
This has been fixed in v1.1.3 -> you can get the new version on pypi or github. I should note that while the releases say that the minimum compatible Synapse version for 1.1.3 of the module is Synapse 1.84.0, it should work with older versions of Synapse (but will break some of the tests/dev tooling.) |
Describe the bug
If users on a synapse homeserver with this module get invited from a user via federation the invite is not automatically accepted.
To Reproduce
Steps to reproduce the behavior:
Expected behaviour
The invite is automatically accepted.
Desktop (please complete the following information):
does not apply
Smartphone (please complete the following information):
does not apply
Additional context
The tested homeservers are synapse on version
1.61.1
in a dockerized environment. The module was installed in the container with pip. koyax.org is the federated homeserver and lippesola.de the one with the module installed. lippesola.de has federation whitelisting enabled with koyax.org beeing part of that list. koyax.org has unrestricted federation.Logs
This is the log of the synaspe server with the module installed when a federated user invites a local user.
The text was updated successfully, but these errors were encountered: