Wikipedia talk:Version 1.0 Editorial Team/Index

The WP 1.0 bot is currently offline due to uknown technical reasons. User:Audiodude has applied a preliminary fix and we are working to get it up and running again soon. Thanks for your patience! More information available on the current page at Wikipedia_talk:Version_1.0_Editorial_Team/Index#Bot_is_gutting_many_of_the_tables

Help in setting up the bot

Wanted to create a table for the Philippine politics task force. Created the categories, added the task force to be added to the WikiProject template (requested to) and tagged a few pages with the template, yet there isn't a row for the task force. All help will be appreciated! 🍗TheNuggeteer🍗 (My "blotter") 08:42, 23 March 2025 (UTC)

Categorisation was incomplete. I have added relevant category. Let's see if WP1.0 report is created within the next day. —CX Zoom[he/him] ^{(let's talk • {C•X})} 10:12, 23 March 2025 (UTC)

wp1.openzim.org malfunctioning?

wp1.openzim.org seems to be malfunctioning. When I click from tables to get a list of articles, none come up. I just get 3 blinking blue circles. Nurg (talk) 01:37, 26 March 2025 (UTC)

It's working again now. Nurg (talk) 05:13, 26 March 2025 (UTC)

Bot seems to have stopped running

It has not made an edit for 30 hours. Nurg (talk) 21:23, 6 April 2025 (UTC)

3 days now. Anyone know where the on/off switch is? The-Pope (talk) 14:45, 8 April 2025 (UTC)

Ping User:Audiodude, who has helped previously – are you able to advise this time? Thanks. Nurg (talk) 21:23, 8 April 2025 (UTC)

I've deployed the latest changes to the server, which includes a full restart, so let's see if it runs tonight. audiodude (talk) 22:37, 8 April 2025 (UTC)

Okay, it looks like an update from earlier this week broke table/log uploading (though the backend was still updated). I fixed it about halfway through it's current run ("Kentucky") so it will be incomplete tonight but should work fine tomorrow night. Thanks for everybody's patience, and please do (a)mention me in the future with any issues. I've tried to set up watchlist/emailing for this page but have never gotten it to work! audiodude (talk) 02:39, 9 April 2025 (UTC)

Bot is gutting many of the tables

The bot seems to be largely gutting many of the tables. Eg, Auckland, Applied linguistics, Austria. Nurg (talk) 05:25, 14 May 2025 (UTC)

I've blocked for now. Firsfron of Ronchester 05:37, 14 May 2025 (UTC)

Looking into it now. Seems to be a problem with the bot contacting the Wikipedia API? audiodude (talk) 16:03, 14 May 2025 (UTC)

Oh nevermind, I think those API log messages are a result of being blocked. audiodude (talk) 16:13, 14 May 2025 (UTC)

Okay I have literally no idea what happened, and I haven't changed anything, but manual runs of the bot are running properly now.

I see this in the logs from May 14 ~00:00 UTC (yesterday)

> wp1-update-2.log.2:INFO:wp1.logic.project:Deleted 32228 ratings that were empty for project: Austria

But it's not clear why the bot thought those ratings were "empty".

I also have about a million (!) lines of:

> WARNING:wp1.logic.api.page:Error contacting API, returning None

The API is only contacted in the case that an article that was previously rated can't be found, to check for article move metadata. So yes, maybe the API was broken, but why did the tool think the article was deleted/moved in the first place?

This is the current page in the tool, which would be uploaded to en wiki, after a manual run of Austria:

https://wp1.openzim.org/#/project/Austria

The only problem now is that the next time the bot runs, it will see all of these 32k articles as "new" and write that into the Wikipedia:Version_1.0_Editorial_Team/Austria_articles_by_quality_log, which will probably be too large to upload (like the current version, which is likely "everything got deleted" messages). So I think what we want to do is purge the logs after the next successful run, and they will start being created again on the next day.

I've created an issue to track adding a failsafe so that this doesn't occur in the future: https://github.com/openzim/wp1/issues/868 audiodude (talk) 17:52, 14 May 2025 (UTC)

cc: @Kelson audiodude (talk) 17:52, 14 May 2025 (UTC)

Audiodude, if you think the process should be ok now, do you think the bot can be unblocked now, rather than just waiting for the block to expire? Nurg (talk) 01:00, 15 May 2025 (UTC)

No, I don't think it's a good idea to remove the block early. I honestly don't think it's a good idea to remove it at all until we have a better idea of what caused this and how to prevent it in the future. audiodude (talk) 03:17, 15 May 2025 (UTC)

I've extended the block indefinitely until it can be determined that the problem is resolved, or what caused the issue is known. Firsfron of Ronchester 03:54, 15 May 2025 (UTC)

I've merged and deployed https://github.com/openzim/wp1/pull/869 which addresses/fixes the issue I raised earlier, to hopefully prevent this from happening in the future. However, I still have no idea what caused it, and I don't have any ideas where or what to look for in that regard. The bot logs aren't helpful here. I guess I'm hoping to get an email along the lines of "FYI tool maintainers: the database was returning garbage briefly a day ago".

Let's take a day or two for @Kelson to weigh in, and then potentially remove the block, after which we will have to purge logs as I mentioned. audiodude (talk) 04:54, 15 May 2025 (UTC)

To be clear, as mentioned in that PR, it is plausible that if the replica database returned an empty list for "FooBar articles by quality", this could happen (which is what my PR aims to address). However, it's not clear why it would return an empty list and not an out-of-band database error. It's not an issue with any of the tables or our query, because those remain unchanged and as I pointed out, manual updates are working.

So really, I think I've narrowed down the problem to "enwiki_p returned an empty list" but I have no idea still what could have caused that. audiodude (talk) 04:57, 15 May 2025 (UTC)

I strongly recommend to open an upstream bug at Phabricator, as current fix in the bot looks like more like a workaround than a fix. Kelson (talk) 05:57, 15 May 2025 (UTC)

Filed a phabricator ticket audiodude (talk) 15:35, 15 May 2025 (UTC)

Thank you. --Rosiestep (talk) 19:51, 16 May 2025 (UTC)

Any update? --Rosiestep (talk) 10:55, 19 May 2025 (UTC)

Thanks for the ping. @Firsfron can you unblock the bot now? I don't expect this to happen again, and we haven't gotten any real response on the phabricator ticket. audiodude (talk) 12:59, 19 May 2025 (UTC)

Okay, I have unblocked. I hope it can be determined what caused the issue. Good luck! Firsfron of Ronchester 17:46, 19 May 2025 (UTC)

Audiodude, Firsfron, Kelson. The problem is still happening. Eg, diffs: Basque, Firefighting. Please block it again. And next time you think the problem is solved and unblock it, please, monitor whether the problem resumes. Nurg (talk) 22:36, 19 May 2025 (UTC)

I have reblocked. I'll continue to monitor this page. Firsfron of Ronchester 22:41, 19 May 2025 (UTC)

Thanks very much for the very speedy response. That's a relief. Nurg (talk) 22:43, 19 May 2025 (UTC)

Thank you @Firsfron and @Nurg for the quick actions. Apologies that I wasn't able to have my finger on the absolute pulse of the bot as soon as it started this evening. We're all volunteers here. I will continue to pursue a permanent resolution to this problem. Thanks again for your patience. audiodude (talk) 00:07, 20 May 2025 (UTC)

Okay I've done more debugging this evening, but haven't come to any real conclusions as to what's going wrong. You can track my progress at https://github.com/openzim/wp1/issues/875 and feel free to leave any technical comments there. audiodude (talk) 05:13, 21 May 2025 (UTC)