-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Repeated setting of .m.rule.is_room_mention
push rule
#27173
Comments
Likely caused by element-hq/synapse#16987 |
This is hammering at 2000 requests per minute. What can I do now but just close Element? Edit: Blocked the runaway request with uBlock Origin |
I can confirm the problem. My Linux Mint has been updating Element in the background and I've seen it in the server logs that the logs are getting cluttered. After some debugging I found this issue here. I downgraded Element desktop from https://packages.element.io/debian/pool/main/e/element-desktop/element-desktop_1.11.61_amd64.deb In the server container logs the following logs is flooding:
The developer console shows the same like in #27246. I have the server version |
Regressed by matrix-org/matrix-js-sdk#4100 |
Steps to reproduce
Element web seems to be sending the following requests in a loop:
PUT /_matrix/client/v3/pushrules/global/override/.m.rule.is_room_mention/enabled
PUT /_matrix/client/v3/pushrules/global/override/.m.rule.is_room_mention/actions
Outcome
What did you expect?
For it to not repeatedly send those requests
What happened instead?
It gets stuck in a loop?
Operating system
Ubuntu
Browser information
Firefox/123.0
URL for webapp
No response
Application version
54ba087-react-0f251d8a55a6-js-78d05942a35a
Homeserver
matrix.org
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: