Page MenuHomePhabricator
Create Task
Maniphest T143286

How did a PageTriage review log entry and notification appear a month after initial page-patrol
Open, Needs TriagePublic
Actions

Description

We're confused as to how these 2 log entries are separated in time.
https://en.wikipedia.org/w/index.php?title=Special:Log&type=&user=&page=High+%28EP%29&tagfilter=&subtype=&hide_patrol_log=0
This should not be possible. (IIUC)

Based on my testing...
The 2 log entries should either appear at the same time, if NPP (Special:NewPagesFeed) is used to patrol the page
e.g. https://test.wikipedia.org/w/index.php?title=Special:Log&page=Test+patrol+5&hide_patrol_log=0
or should require an "unreview" to appear in the middle, if the old patrolled-edits feature is used first, and then NPP is used after.
e.g. https://test.wikipedia.org/w/index.php?title=Special:Log&page=Test+patrol+4&hide_patrol_log=0

Initially reported at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Pages_being_marked_as_patrolled_despite_being_autopatrolled
following a brief discussion at https://en.wikipedia.org/wiki/User_talk:Atlantic306#Review_of_High_.28EP.29
and https://en.wikipedia.org/wiki/User_talk:Ss112#High_EP

Related Objects

Event Timeline

Quiddity created this task.Aug 17 2016, 11:24 PM
Restricted Application added a project: Collaboration-Team-Triage. · View Herald TranscriptAug 17 2016, 11:24 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Xaosflux subscribed.Aug 18 2016, 1:17 AM
Etonkovidova subscribed.EditedAug 18 2016, 6:24 PM

The issue - the patrolled and reviewed events are separated by some time interval - can be easily found/reproduced in betalabs.
In the screenshot below, aside of the problem of multiple patrolling events with the same timestamp, the event "automatically marked revision [#] as patrolled" initially appears cause the page was created by an Autopatrolled user.

Screen Shot 2016-08-18 at 10.31.44 AM.png (599×896 px, 158 KB)

Another example - after a page was created by Autopatrolled user, another reviewed add a tag:
Screen Shot 2016-08-18 at 11.13.05 AM.png (108×1 px, 50 KB)

However, testing further, there are events that make a page to be a subject to review again

  1. deleting
  2. unreviewing
  3. tagging the previously reviewed page

All those event will be recorded in the Special:Log - at least, it's correct for betalabs environment.

Quiddity updated the task description. (Show Details)Aug 26 2016, 5:03 PM
Quiddity added a comment.Aug 26 2016, 5:07 PM

@Etonkovidova I'm confused... What steps did you follow to get the 3 "marked as reviewed" in a row?

I can't see any deletion/unreviewing/tagging in the page history or logs of that test page, which you suggested were the events necessary for making it subject to review again:
https://en.wikipedia.beta.wmflabs.org/w/index.php?title=Special:Log&page=Mavetuna12&hide_patrol_log=0&hide_review_log=0
https://en.wikipedia.beta.wmflabs.org/w/index.php?title=Mavetuna12&action=history

Etonkovidova added a comment.EditedAug 26 2016, 11:31 PM

@Quiddity
(1) the multiple identical records 'marked the page as reviewed' is just a bug - filed as T127110: PageTriage: Reviewing a page gives "Direct editing via API is not supported for content model flow-board used by a user" which was marked as duplicate to T127112: PageTriage: 'Mark for deletion' gives "Failed to notify author on talk page" for user with flow-enabled User talk page. .

(2) I looked again into the reported issue and it looks even more puzzling:
According to db, 'High (EP)' is supposed to have three records, but only two are displayed.

s1-analytics-slave [enwiki]> select log_title,log_user_text, log_type, log_action, log_timestamp from logging  where log_title = 'High_(EP)';
+-----------+---------------+---------------------+------------+----------------+
| log_title | log_user_text | log_type            | log_action | log_timestamp  |
+-----------+---------------+---------------------+------------+----------------+
| High_(EP) | Ss112         | patrol              | autopatrol | 20160728154224 |
| High_(EP) | Atlantic306   | pagetriage-curation | reviewed   | 20160816153607 |
| High_(EP) | Ss112         | patrol              | patrol     | 20160816155438 |
+-----------+---------------+---------------------+------------+----------------+
3 rows in set (0.00 sec)

I found the identical case in betalabs - and Special:Logs displays only one record for the page 'Mavetuna':

 select log_title, log_action, log_type, log_timestamp, log_user_text from logging where log_title='Mavetuna';
+-----------+------------+---------------------+----------------+---------------+
| log_title | log_action | log_type            | log_timestamp  | log_user_text |
+-----------+------------+---------------------+----------------+---------------+
| Mavetuna  | patrol     | patrol              | 20150617235202 | Etonkovidova  |
| Mavetuna  | patrol     | patrol              | 20160222200247 | ET70          |
| Mavetuna  | reviewed   | pagetriage-curation | 20160818174944 | ET1           |
+-----------+------------+---------------------+----------------+---------------+
3 rows in set (0.08 sec)
  • Why many pages have multiple patrol actions?

The following query gives 89 records (betalabs enwiki) - and few of them are like 'Mavetuna' - do not indicate that pages were deleted or some other changes in pages' status.

select log_title, log_action, count(*) as c from logging where log_type='patrol' and log_action='patrol'  group by log_title having c>1 order by c desc;
• jmatazzoni edited projects, added Collab-Team-Q1-July-Sep-2016; removed Collaboration-Team-Triage.Aug 29 2016, 10:40 PM
• jmatazzoni moved this task from Untriaged to Ready for Pickup on the Collab-Team-Q1-July-Sep-2016 board.
• jmatazzoni edited projects, added Collaboration-Team-Triage (Collab-Team-Q2-Oct-Dec-2016); removed Collab-Team-Q1-July-Sep-2016.Oct 4 2016, 10:43 PM
• jmatazzoni moved this task from Untriaged to Ready for Pickup on the Collaboration-Team-Triage (Collab-Team-Q2-Oct-Dec-2016) board.Oct 4 2016, 10:48 PM
• jmatazzoni edited projects, added Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017); removed Collaboration-Team-Triage (Collab-Team-Q2-Oct-Dec-2016).Jan 5 2017, 7:47 PM
• jmatazzoni moved this task from Untriaged to Ready for Pickup on the Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017) board.Jan 5 2017, 8:03 PM
• jmatazzoni edited projects, added Collaboration-Team-Triage; removed Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017).Apr 12 2017, 6:15 PM
• jmatazzoni moved this task from Untriaged to Near-Term Interest on the Collaboration-Team-Triage board.
Restricted Application added a project: Growth-Team. · View Herald TranscriptFeb 26 2019, 8:34 AM
MBinder_WMF added a project: Growth-Team-Filtering.Apr 15 2021, 6:59 PM
Aklapper removed a project: Collaboration-Team-Triage.May 25 2021, 9:09 PM
Aklapper removed a project: PageTriage.Oct 17 2023, 9:06 PM
Aklapper edited projects, added PageTriage; removed Growth-Team.Oct 17 2023, 9:11 PM
Restricted Application added a project: Growth-Team. · View Herald TranscriptOct 17 2023, 9:11 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits