matrix-org / matrix-appservice-irc

Node.js IRC bridge for Matrix
Apache License 2.0
460 stars 149 forks source link

allowUnconnectedMatrixUsers keeps resetting itself #1721

Open erciccione opened 1 year ago

erciccione commented 1 year ago

We had a problem of messages from IRC not being related initially. On suggestion of Matrix' team we set "allowUnconnectedMatrixUsers": true. This works, but for some reason it's not persistent. After noticing the first messages were still not relayed we found out that allowUnconnectedMatrixUsers removes itself from time to time, resulting in messages from IRC getting lost. Sending the state event fixes the problem until the next reset.

This seems to happen only on one room (https://matrix.to/#/#monero-site:monero.social), while in other room with the same settings stays persistently.

Half-Shot commented 1 year ago

This sounds like the infamous state reset bug to me, I've asked how to proceed with this. (I don't think the bridge can do much about it).

erciccione commented 1 year ago

The problem persists. I'm trying to remove and then readd the bridge, but i keep getting an error:

Screenshot_20230608_084149

I have the feeling there is something borked that is causing or contributing to the problem. When i try to relink the channel, the "channel operator nick" is not found and i get the error message "could not get operator nick", even if the operator is definitely there (it's me). Maybe some support directly on the channel would be helpful (my nick on matrix: @erc:cryptoriot.org)

edit:

Apparently now it finds the operators, but when i try to bridge:

Could not request link. Error IRC_DOUBLE_BRIDGE: Room failed validation. You may be attempting to "double bridge" this room. Error: Error: M_FORBIDDEN: Appservice not in room

The room was disconnected before trying to set up a new bridge, and appservice left. I'm still unable to delete the bridge (see screenshot)

quite commented 11 months ago

In https://github.com/matrix-org/matrix-appservice-irc/issues/1652 I have what now seems to be the same issue.