]> git.ipfire.org Git - thirdparty/patchwork.git/commit
notifications: fix notification expiry when no user is associated
authorJeremy Kerr <jk@ozlabs.org>
Sat, 27 Apr 2019 11:12:16 +0000 (19:12 +0800)
committerDaniel Axtens <dja@axtens.net>
Tue, 30 Apr 2019 04:49:45 +0000 (14:49 +1000)
commitd0b79d9dee04aee13c8d64a193a7818f72eeca3b
tree7e65f73aa5bec3dfbaf5599689b8ca58b33e5a88
parentba0883c0fcab7630c64f1782a0d9eeaffa1ade99
notifications: fix notification expiry when no user is associated

It's possible that an EmailConfirmation object will have no associated
user (eg, for email opt-out, which does not require a user object). In
this case, we will see a NULL value for EmailConfirmation.user_id.

However, having a NULL value appear in a SQL 'IN' clause will match
every value. This means that once one of these null-user
EmailConfirmations is present, we will never expire any non-active user
accounts.

This change adds a filter for a valid user_id when we query for active
EmailConfirmation objects. This means we'll have a valid values set to
use in the pending_confs set.

Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
[dja: fix pep8 issue]
Signed-off-by: Daniel Axtens <dja@axtens.net>
patchwork/notifications.py