Page MenuHomePhabricator

Make AbuseFilter work on PostgreSQL and SQLite (epic)
Closed, ResolvedPublic

Description

Collection of tasks for known AbuseFilter problems with SQLite and Postgres.

Related Objects

StatusSubtypeAssignedTask
OpenNone
OpenNone
OpenNone
InvalidNone
DeclinedNone
ResolvedNone
ResolvedDaimona
ResolvedDaimona
Resolvedmatej_suchanek
ResolvedDaimona
ResolvedDaimona
Resolvedmatej_suchanek
Resolvedmatej_suchanek
ResolvedPRODUCTION ERRORDaimona
ResolvedDaimona
OpenUmherirrender
ResolvedDaimona
ResolvedMarostegui
ResolvedBstorm
ResolvedDaimona
ResolvedUrbanecm
ResolvedMarostegui
Resolvedrook

Event Timeline

Daimona renamed this task from Make AbuseFilter work on PostgreSQL and SQLite to Make AbuseFilter work on PostgreSQL and SQLite (tracking).Sep 6 2018, 3:34 PM
Daimona triaged this task as Medium priority.
Jdforrester-WMF renamed this task from Make AbuseFilter work on PostgreSQL and SQLite (tracking) to Make AbuseFilter work on PostgreSQL and SQLite (epic).Feb 24 2020, 10:33 PM
Reedy changed the task status from Open to Stalled.Jul 31 2020, 5:18 PM
Reedy added a subscriber: Reedy.

Marking stalled due to subtask needing solving first

Well, that's half the work done, right? ;-)

Yay :-) Only T220791 is left to do now.

Daimona claimed this task.

All subtasks done. While T259377 is still open, it doesn't prevent AF from working on postgres/SQLite

hashar added a subscriber: hashar.

The CI change https://gerrit.wikimedia.org/r/c/integration/config/+/653121 enforces Sqlite for AbuseFilter but since CI inject other extensions they should be checked against Sqlite as well. T307990 is about dropping Sqlite support in CheckUser which ends up causing AbuseFilter CI to break.