Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Push Rules aren't always enabled by default #7743

Closed
t3chguy opened this issue Jun 25, 2020 · 3 comments
Closed

Push Rules aren't always enabled by default #7743

t3chguy opened this issue Jun 25, 2020 · 3 comments
Assignees
Labels
A-Spec-Compliance places where synapse does not conform to the spec z-bug (Deprecated Label)

Comments

@t3chguy
Copy link
Member

t3chguy commented Jun 25, 2020

As per the spec https://matrix.org/docs/spec/client_server/r0.6.1#put-matrix-client-r0-pushrules-scope-kind-ruleid

When creating push rules, they MUST be enabled by default.

But in Synapse if you add a push rule, disable it, remove it and re-add a push rule with the same ID then it'll be disabled.

I guess the entry in the push_rules_enable table isn't getting cleared out
This will need to be fixed retroactively for already deleted push rules too.
Looks to also be an opportunity to purge a bunch of stale data from that table for rules which no longer exist.

@t3chguy t3chguy added the A-Spec-Compliance places where synapse does not conform to the spec label Jun 25, 2020
@richvdh
Copy link
Member

richvdh commented Jun 25, 2020

this is closely related to matrix-org/matrix-spec-proposals#2655: the fact that synapse permits hidden "enabled" state about non-existent pushrules.

@richvdh
Copy link
Member

richvdh commented Jun 25, 2020

the impact of this is that when somebody creates a new "keyword" to be notified on, it might not work.

@richvdh
Copy link
Member

richvdh commented Aug 11, 2020

dup #1475

@richvdh richvdh closed this as completed Aug 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Spec-Compliance places where synapse does not conform to the spec z-bug (Deprecated Label)
Projects
None yet
Development

No branches or pull requests

4 participants