Last modified: 2014-10-07 07:45:45 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T57032, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 55032 - create "checkpage" option and global "-enable" argument
create "checkpage" option and global "-enable" argument
Status: NEW
Product: Pywikibot
Classification: Unclassified
General (Other open bugs)
core-(2.0)
All All
: High enhancement
: ---
Assigned To: Ricordisamoa
https://sourceforge.net/p/pywikipedia...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-05 04:07 UTC by Kunal Mehta (Legoktm)
Modified: 2014-10-07 07:45 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Kunal Mehta (Legoktm) 2013-10-05 04:07:06 UTC
Originally from: http://sourceforge.net/p/pywikipediabot/feature-requests/312/
Reported by: avicennasis
Created on: 2012-06-18 05:17:33
Subject: -enable arg to all scripts
Original description:
It would be handy to have an optional -enable "Checkpage" option built into scripts by default - so that a bot can deactivated by non-admins, if so needed.
Comment 1 Kunal Mehta (Legoktm) 2013-10-05 04:07:08 UTC
What is the behaviour you would want/expect when 'Checkpage' is enabled?
Comment 2 Kunal Mehta (Legoktm) 2013-10-05 04:07:09 UTC
A simple boolean value - if the arg is used, read checkpage - if 'true', continue script - if false, stop and exit script.

I know some of the scripts have a "enablePage" - but a lot of them don't.
Comment 3 Kunal Mehta (Legoktm) 2013-10-05 04:07:11 UTC
That doesn't tell me anything about what it should do. What is 'checkpage'? What should the bot do with it? When? What should it do in which case?
Comment 4 Kunal Mehta (Legoktm) 2013-10-05 04:07:13 UTC
Exactly what the '-enable:' parameter does in lonelypages.py - http://svn.wikimedia.org/svnroot/pywikipedia/trunk/pywikipedia/lonelypages.py
Comment 5 Kunal Mehta (Legoktm) 2013-10-05 04:07:15 UTC
This behavior is not the same as blocking a bot by admins; it only prohibits the next start of the bot. So I am not sure if this is what you want to.
Comment 6 Kunal Mehta (Legoktm) 2013-10-05 04:07:16 UTC
True, it is different then an admin stopping the bot via blocking, which of course would be instant. I was thinking more of implementations on cron - allowing any user to 'disable' the next run of a cronjob'd script until the BotOp is online/able to address a problem that may have arisen. 

\(Alternatively, one could rewrite the -enable option to be checked every 10-25 pages, and so stop a bot from running even in 'mid-script'.\)
Comment 7 Ricordisamoa 2014-06-06 18:33:02 UTC
reflinks.py also implements a similar system ('stopPage'). It checks the latest revid (not the content), but every 20 edits.
Comment 8 Gerrit Notification Bot 2014-06-06 19:07:59 UTC
Change 137980 had a related patch set uploaded by Ricordisamoa:
PROOF-OF-CONCEPT: check own talk, a custom page, and notifications

https://gerrit.wikimedia.org/r/137980
Comment 9 John Mark Vandenberg 2014-10-07 07:45:45 UTC
no code to review yet

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links