Open mvgorcum opened 2 years ago
I did a bit more experimentation, and I think I found the cause of this issue:
The room in question was added with the production.yaml
config, but not through !mjolnir rooms add
. After I set the room as protected using !mjolnir rooms add
(while not removing it from the config) the bot did set the ACL as expected.
While my issue is solved this is still unexpected behaviour so I'll leave this issue open.
Oh, that cause does make things a lot easier to understand on our end. Thanks for doing the follow up and investigating!
Happy to help!
Describe the bug We set a ban on a server in the management room, but this ACL ban was not applied in the #fdroid:f-droid.org room.
To Reproduce Steps to reproduce the behavior:
!mjolnir ban coc example.com spam
in the management roomExpected behavior ACL gets applied in #fdroid:f-droid.org
Additional context The room in question does already have an ACL list, with a few more servers than are set in mjolnir, but the new server (example.com) does not get added to said list.