Page MenuHomePhabricator

in bot mode, after 50k-ish good edits bot started randomly blanking pages
Open, Needs TriagePublicBUG REPORT

Description

Monkbot task 15 is a simple task that replaces {{xx icon}} templates with {{in lang|xx}}; Monkbot never does general fixes. After 50k-ish good edits an editor halted monkbot with a post to its talk page. See its contributions page:

  • started blanking here; first bad edit at 20:26, 30 December 2019
  • task was halted here; last bad edit at 20:47, 30 December 2019

Before being halted, task 15 blanked about 160 articles.

After the task was halted, I rolled back all of the bad edits; closed the instance of awb that was running the bot; restarted awb, restarted the bot task. The first 160-ish bot edits after the task was restarted are those articles that were blanked; none of them were blanked a second time.

I'm pretty sure that it isn't this task; I have seen this happen before on other tasks doing wholly different jobs. The single thing that is the same is that I have allowed awb to run for long periods of time without restarting. If there is a time limit that exists, perhaps awb should require a restart when that limit is reached. Perhaps awb can detect when it is blanking a page and halt with an appropriate message.

Event Timeline

This happen to me too twice before. Yesterday, I was using AWB for purging pages, (adding an empty line to a file page, which is ignored as an edit but it refreshes the page). Due to T245349, I need to purge pages after adding SDC statements. I added ~100-150k statements and purged about that many file pages before something went wrong and AWB started blanking pages, see here. It blanked about 200 of them before sameone noticed a problem and stopped the bot. Restarting AWB fixed the issue.

Ideally we could fix AWB so it does not do that, but another possible solution would be, some option "stop the bot if blanking pages" or something.

Ideally we could fix AWB so it does not do that

It almost sounds like people think AWB is doing it purposely ;)

Reproducing it is obviously pretty hard :(

No I was not thinking that and sorry if I sounded unpleasant. I use AWB a LOT and this issue happen to me only twice, so it is a very rare event. I was wandering if the issue was not related somehow to a large number of edits I was making. I tend to keep it always open and just give it new tasks. I will be adding SDC statements (kind of like wikidata statements) to 1.3 M pages (using QuickStatements) and if I do not want to add them twice to the same file, I have to purge the page with nul edit adter adding each statement. So I will be doing it a lot. I know reproducing it is hard, that is why I proposed something that would detect the outcome (page blanking) and stop the bot before it makes much damage. In majority of the cases, page blanking is not expected outcome and maybe in those cases you would need to turn this option off. Another way of inquiry would be to see if there is some (improbable) set of conditions which would lead to AWB behaving that way.

It seems to have happen again, as reported at c:User_talk:Jarekt#Your_bot_blanked_hundreds_of_pages. Due to bug T251507 my bot is running thousands of "touch" operations using AWB, by adding a single line to a page, which is ignored by the software but it does trigger page refresh. Those edits do not show in the user contributions or page history. However once in a while AWB goes berserk.

See log

Aklapper changed the subtype of this task from "Task" to "Bug Report".Nov 22 2022, 5:19 PM