Travis Ralston
Travis Ralston
another deployment which protects all joined rooms appears to be trying to apply bans to a room it's no longer in as well - maybe mjolnir forgot how to untrack...
in the first case, we appear to have had the room listed multiple times in the account data for the bot, so it wasn't removing it enough times or something....
It can't tell the difference between this and a glob, and generally does not try to protect you from yourself for intentional reasons.
Related: https://github.com/matrix-org/synapse/issues/2133
we can't seem to upgrade for other reasons at the moment, namely related to how the IPFS modules are set up.
Project now (theoretically) supports Go 1.18 instead.
This is a lot harder to do than it seems: Ideally the API lists all rooms, however that's not well exposed by Synapse. Additionally, the use of a shared secret...
Turns out the downloads cache is also used for thumbnails. We probably want to split this out into two caches.
What sorts of errors are you seeing in the logs?
and just to confirm, the process isn't unintentionally limited in max open files? (systemd, ulimits, etc)