Log M_FORBIDDEN room metadata failures as warnings #1
Loading…
Reference in a new issue
No description provided.
Delete branch "roommeta-forbidden-warn"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When the bridge is added to an existing Matrix room (e.g. adopted via
!xmpp bridge), the bot does not necessarily have the power level required forcom.beeper.room_featuresand similar metadata state events (eventauth: sender ... is not allowed to send event. 15 < 100).This is expected and non-fatal — the capability update is simply skipped — so it is now logged at warn level instead of error, keeping
ERRlines meaningful.Seen in production logs of the XMPP bridge (portal on a foreign homeserver): every portal sync produced an
ERR Failed to set room metadataline.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.