Skip to content
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

Nightly and develop spam "global push rule" messages in the console #27147

Closed
davidegirardi opened this issue Mar 11, 2024 · 1 comment
Closed
Labels

Comments

@davidegirardi
Copy link

Steps to reproduce

  1. Open Element Desktop Nightly or develop.element.io
  2. Open the Electron/browser console
  3. See hundreds of these messages per second:
Missing default global push rule .m.rule.suppress_notices
Missing default global push rule .m.rule.invite_for_me
Missing default global push rule .m.rule.member_event
Missing default global push rule .m.rule.is_user_mention
Missing default global push rule .m.rule.contains_display_name
Adding default global push rule .m.rule.is_room_mention
Missing default global push rule .m.rule.roomnotif
Missing default global push rule .m.rule.tombstone
Adding default global push rule .m.rule.reaction
Missing default global push rule .m.rule.room.server_acl
Adding default global push rule .org.matrix.msc3786.rule.room.server_acl
Missing default global push rule .m.rule.suppress_edits
Missing default global push rule .m.rule.encrypted_room_one_to_one

Outcome

What did you expect?

A semi-quiet console

What happened instead?

Spamming.

Operating system

Arch linux

Application version

Element Nightly version: 2024031001 Crypto version: Olm 3.2.15 and Element version: a0c90f9-react-8e68d5d6be14-js-30311524443d Crypto version: Rust SDK 0.7.0 (b1918e9), Vodozemac 0.5.1

How did you install the app?

No response

Homeserver

No response

Will you send logs?

Yes

@t3chguy
Copy link
Member

t3chguy commented Mar 11, 2024

This is expected, the server has left your client in an invalid (not spec compliant state) due to a bug: element-hq/synapse#16987 - and each time the error manifests due to missing data the warning is logged.

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants