User talk:Shubinator

From Wikipedia, the free encyclopedia
  (Redirected from User talk:DYKUpdateBot)
Jump to: navigation, search

Talk

Questions? Comments? Advice? Talk to me.

"Did you know...?"
Discussion WT:DYK
Rules WP:DYK
Supplementary rules WP:DYKSG
Noms (awaiting approval) WP:DYKN
Reviewing guide WP:DYKR
Noms (approved) WP:DYKNA
Preps & Queues T:DYK/Q
Currently on Main Page
Main Page errors WP:ERRORS
Archive of DYKs WP:DYKA
Stats WP:DYKSTATS

Contents

Issues with DYKcheck?[edit]

Hi Shubinator, I was attempting to run DYKcheck on two articles tonight (including Soaring Stones) and I ran into some issues. The check never finished processing and only output the following lines:

  • Prose size (text only): 3631 characters (584 words) ''readable prose size''
  • Article created by Another Believer on April 17, 2015


  • Article has not been expanded 5x since it was created.

The third line is blank and the DYK eligibility scan states that it is still in progress. I know that the article fails the DYK check, but it does not tell me so. Do you know why?

Thank you, MJ94 (talk) 07:53, 5 January 2016 (UTC)

How curious. I'm seeing the bug on Google Chrome, but not Internet Explorer. Which browser are you using? Looks like Google Chrome is having trouble parsing the date the article was promoted to GA. Shubinator (talk) 07:12, 6 January 2016 (UTC)
I believe I've fixed the bug with this change. Can you check if the bug is fixed on your end? Shubinator (talk) 04:44, 7 January 2016 (UTC)
Sorry for the delay; yes, I am using Chrome, and it seems to be fixed now. Thank you! MJ94 (talk) 04:57, 28 January 2016 (UTC)
Happy to help :) Shubinator (talk) 16:24, 28 January 2016 (UTC)

The easiest feature request ever[edit]

A bot is going around replacing transclusions of template redirects (example). It would save some unnecessary edits if DYKUpdateBot started using {{DYK talk}} instead of {{dyktalk}}. MANdARAX  XAЯAbИAM 08:26, 12 January 2016 (UTC)

Done :) Shubinator (talk) 19:41, 16 January 2016 (UTC)

Please check DYKUpdateBot[edit]

as it missed the last update on 13 January, thanks. Materialscientist (talk) 02:35, 13 January 2016 (UTC)

Both bots are having issues editing Wikipedia, and unfortunately the issues didn't disappear after a restart. I'll dig deeper tomorrow when I'm more awake. Shubinator (talk) 07:47, 13 January 2016 (UTC)
Curiosity won over sleep. The bots are "seeing" Sorry! We could not process your edit due to a loss of session data. every time they try to edit. Feels like it's due to a recent MediaWiki update since the bots' edit/login code hasn't changed in months. Shubinator (talk) 09:17, 13 January 2016 (UTC)
Fixed. Not the most elegant fix in the world, hopefully when I have more time I can revisit it. Thanks everyone for keeping things rolling while the bots were down :) Shubinator (talk) 05:34, 14 January 2016 (UTC)

Request/bug carryforward[edit]

I've just archived a bunch of stuff from my talk page. There are a few requests/bugs still on my list though:

  • DYKHousekeepingBot sometimes notifies nominators of untranscluded nominations after human error while closing the nomination. Original conversation here. I dug into the records and this bug cropped up 8 times in the last ~16 months, for an average of once every two months. Tweaking DYKHousekeepingBot to ignore nominations with "The result was:" in the wikitext should get the bot to do the right thing in these cases.
  • More informative DYKUpdateBot error edit summaries and leaving around unresolved errors, requested by User:Mandarax.
  • DYKUpdateBot's incorrect handling of existing blank dykentry parameters in {{ArticleHistory}}. Original conversation here. I skimmed through the records for the past two months and this bug appeared once.

On a slightly related note, it looks like MediaWiki authentication changes will be rolled out in the next few weeks, which will disrupt the bots.

If I missed/forgot something, let me know! Shubinator (talk) 05:49, 17 January 2016 (UTC)

DYKHousekeepingBot okay?[edit]

I noticed DYKHousekeepingBot has been inactive for seven hours, which is strange considering how frequently this bot edits. Jolly Ω Janner 21:57, 21 January 2016 (UTC)

Back in action! Thanks for pinging me :) Shubinator (talk) 07:01, 22 January 2016 (UTC)

DYKHousekeepingBot appears to be down[edit]

Shubinator, it's currently 22:47, and the DYKHousekeepingBot hasn't done an update since 14:41. As there have been a great many changes to the list of nominations in the past eight hours, the bot would appear to be down. It strikes me that DYKUpdateBot may well be down, too. Can you please check them? Many thanks. I'll drop a note to our manual updaters, so they know to keep an eye out at midnight in case DYKUpdateBot isn't awake then. BlueMoonset (talk) 22:51, 21 January 2016 (UTC)

Apparent cause of the bots being down due to OS maintenance on the servers that required reboots. --Allen3 talk 00:14, 22 January 2016 (UTC)
Started up both bots. Thanks everyone for stepping in! Shubinator (talk) 07:00, 22 January 2016 (UTC)
Thank you for getting them back up and running. It's good to see a new DYKHousekeepingBot report. BlueMoonset (talk) 07:06, 22 January 2016 (UTC)

DYKUpdateBot failed to complete 12:00 27 Jan 2016 update.[edit]

DYKUpdateBot appears to have halted in the middle of the 12:00 27 January 2016 (UTC) update. The bot completed the user talk page credits but failed to add a {{DYKfile}} template to File:Fleet Street. By James Valentine c.1890..jpg, clear Template:Did you know/Queue/1, or update Template:Did you know/Queue/Next. The bot has also failed to clear a test message placed into User:DYKUpdateBot/Errors‎. DYKHousekeepingBot appears to be operating normally. A glance through the Labs-l mailing list finds some recent NFS problems so this may be server related. I will leave things alone till 20:00 or 22:00 (UTC) in case you get a chance to look at the situation but will manually complete the incomplete update before the 00:00 28 Jan update is scheduled to run if needed. --Allen3 talk 13:18, 27 January 2016 (UTC)

Looks like the bot was having trouble tagging the file, unfortunately I don't have time to dig deeper. I've restarted the bot, hopefully the issue won't crop up again on the next update. Thanks for pinging me! Shubinator (talk) 16:03, 27 January 2016 (UTC)

Repeat of image tagging problem[edit]

It appears the problem with tagging an image file has returned. The 12:00 February 26, 2016 update by DYKUpdateBot completed all the userpage notifications but the image tag at File:Mells Somerset2.JPG is still pending. --Allen3 talk 12:15, 26 February 2016 (UTC)

Curious. Might be related to MediaWiki's authentication changes; I'll try to update the bot with the auth changes this weekend. In the meantime looks like the bot's auto-reset kicked in and it's back up and running :) Shubinator (talk) 07:44, 27 February 2016 (UTC)
Fell sick this weekend with cold/allergies, digging deeper will have to wait :( Shubinator (talk) 07:51, 29 February 2016 (UTC)

DYKUpdateBot missed 00:00 20 Feb 2016 update[edit]

DYKUpdateBot missed the latest update and ‎DYKHousekeepingBot has not made an update for over 5 hours. There was a series of reboots on the Labs servers today (a continuation of yesterday's security reboots), so that is the most likely cause of the outage. Please check/restart things when you get a chance. --Allen3 talk 00:32, 20 February 2016 (UTC)

Both bots restarted! Thanks for letting me know :) Shubinator (talk) 00:52, 20 February 2016 (UTC)

The DYKUpdateBot makes February 29 red[edit]

Please have a look. The DYKUpdateBot makes all hooks for February 29 red at Wikipedia:Did you know/DYK hook count, even though those hooks are clearly not yet late. Must have something to do with today being leap day and all? Not sure how easy this is to fix, but it sure is an eyesore. Well, have a nice day regardless!—♦♦ AMBER(ЯʘCK) 11:59, 29 February 2016 (UTC)

Actually, that would be DYKHousekeepingBot's issue, but it looks odd either way to have the current date be light red; that's only supposed to happen for over-seven-days-old dates and for dates in the future. Since the 29th is not in the future, something ought to be done. (If it isn't done before midnight UTC, it's going to be interesting to see whether the 29th stays that color, and whether March 1 will be the same color or the normal white.) BlueMoonset (talk) 19:06, 29 February 2016 (UTC)
Well, things seem to be fixed right now. I'm betting it has to do with February 29 being leap day, and the algorithm not properly accounting for that. But now it's March, the issue seems to have resolved itself. Hooray! —♦♦ AMBER(ЯʘCK) 10:04, 1 March 2016 (UTC)
Follow-up: now that it's March 8, and February 29 should be back in the (light) red, it's still white. I imagine that it will change color along with March 1, a bit over 20 hours from now, but it's clear that the algorithm, whatever it is, can't properly handle leap day. The good news: you have nearly four years to fix it for next time. ;-) BlueMoonset (talk) 03:41, 8 March 2016 (UTC)

File:E Minas Geraes C.jpeg listed at Redirects for discussion[edit]

Information.svg

An editor has asked for a discussion to address the redirect File:E Minas Geraes C.jpeg. Since you had some involvement with the File:E Minas Geraes C.jpeg redirect, you might want to participate in the redirect discussion if you have not already done so. Stefan2 (talk) 20:51, 5 March 2016 (UTC)

DYKUpdateBot missed an update on 24 March[edit]

Please have a look. Materialscientist (talk) 01:27, 24 March 2016 (UTC)

Both bots back up and running :) Looks like the Labs server was restarted, which brought down the bots. Thanks for pinging me! Shubinator (talk) 02:13, 24 March 2016 (UTC)
Shubinator, DYKUpdateBot, at least, is down again: its most recent edit was at 12:48 UTC, with no sign of activity, and an update due at 00:31 UTC, about 45 minutes ago. By contrast, the DYKHousekeepingBot did an update about 46 minutes ago, at 00:30 UTC, and continued working all day yesterday. I don't know whether it didn't do a new update at 01:00 because it finally died, or because there was nothing to do. Please take a look as soon as you can. Many thanks. BlueMoonset (talk) 01:21, 26 March 2016 (UTC)
Follow-up: DYKHousekeepingBot did an update at 01:31 UTC, ten minutes after I posted the above, so it seems that only DYKUpdateBot is hors de combat. I hope you see this soon and can restored it to health. Thank you. BlueMoonset (talk) 01:49, 26 March 2016 (UTC)
Further follow-up: DYKUpdateBot started updating at 02:11 UTC, finishing at 02:13 UTC. I have no idea why it didn't update at the scheduled 00:31 UTC, nor do I know why it set the time of the next update at 12:16 UTC—11 hours and 45 minutes after the scheduled start, rather than 11 hours and 45 minutes after the actual start of 02:11 (which would have been 13:56). Shubinator, you can investigate when you see this, but with the main page having been refreshed, the major urgency is gone. If you do want to adjust the time of the next update from 12:16 to 13:56, that would be nice, so the current set gets nearly 12 hours instead of barely 10. Thank you. BlueMoonset (talk) 03:41, 26 March 2016 (UTC)
Unfortunately the logs don't have many clues. The bot did wake up at 00:31 UTC and tried to update, which is why the next update time was set "correctly"; unfortunately the bot ran into trouble attempting to edit Wikipedia. I've shifted the next update time as suggested, and will hopefully find more time soon to make adjustments to the bot. Shubinator (talk) 05:43, 26 March 2016 (UTC)

Major infrastructure migration next week (Tuesday and Thursday, 14:00 UTC)[edit]

Shubinator, I wasn't sure whether you had seen the notification for this one, but it's being displayed at the top of the Watchlist page: Wikimedia Technical Operations is planning a major infrastructure migration on Tuesday, 19 April and Thursday, 21 April, starting at 14:00 UTC. This process is expected to take 15 to 30 minutes each time. During these times, you will be able to read, but not edit any page. The team apologizes for the disruption.

Assuming DYK doesn't get unmoored from its noon/midnight schedule (not a safe assumption, alas, as prep builders haven't been that active), that would mean a check before midnight on those days to be sure the DYK bots don't need to be restarted. I have no idea whether this even fits your schedule, but I thought a heads up now might avoid bot issues later. Thanks as always for keeping the bots running. BlueMoonset (talk) 21:35, 14 April 2016 (UTC)

Thanks for the heads up! I'll aim to check in on the bots at around 15:00 UTC on those days. Shubinator (talk) 04:17, 15 April 2016 (UTC)
DYKUpdateBot looks good, DYKHousekeepingBot is being a bit weird. I'll manually restart DYKHousekeepingBot in ~12 hours if it's still misbehaving. Shubinator (talk) 15:20, 19 April 2016 (UTC)
Both bots look healthy today :) Shubinator (talk) 15:17, 21 April 2016 (UTC)

DYKUpdateBot didn't finish final steps at 14:08[edit]

Shubinator, DYKUpdateBot promoted Queue 3 to the main page at 14:06, but didn't finish the final two steps: clearing out Queue 3 at the end, and setting the next queue to be Queue 4. Both of those steps have been done by hand. So far as I can tell, it did all of the talk page notifications. We'll find out at 01:51 UTC whether the next main-page promotion starts on schedule. (Queue 4 is ready to go.) I thought you'd want to know about this hiccup. BlueMoonset (talk) 18:10, 4 May 2016 (UTC)

Looks like DYKUpdateBot is back to normal. Thanks for letting me know! It feels like we've seen the same bug crop up a few times now...I'm hoping I can dig in later this month and find the pattern. Shubinator (talk) 23:25, 4 May 2016 (UTC)
Saw another instance of this problem with the 00:00 23 May 2016 (UTC) update. As in the past, manually completing the update (incrementing the count at Template:Did you know/Queue/Next and clearing the queue page from the incomplete update) woke DYKUpdateBot from its slumber. --Allen3 talk 12:49, 23 May 2016 (UTC)
Good to know, thanks for the additional data point! Shubinator (talk) 19:17, 23 May 2016 (UTC)
You can add the 12:23 24 May 2014 (UTC) update as another data point. Update manually completed. --Allen3 talk 12:40, 24 May 2016 (UTC)
Thanks! Shubinator (talk) 13:45, 24 May 2016 (UTC)
The 12:00 28 May 2016 (UTC) update was a repeat of the problem. --Allen3 talk 12:38, 28 May 2016 (UTC)
  • The problem repeated with the 12:00 6 June 2016 (UTC) update. --Allen3 talk 13:05, 6 June 2016 (UTC)

Gender-based price discrimination DYK nomination[edit]

Hello,

I recieved your message indicating that step 3 for my DYK nomination of the gender-based price discrimination page. However, I added my nomination to the May 6th date on the nominations page per step 3. Can you let me know if I did something wrong. I am unfamiliar with this process.

Thank you

FPizzo (talk) 12:35, 13 May 2016 (UTC)

(talk page stalker) FPizzo, you received the message because you originally created a nomination for Template:Did you know nominations/Gender-Based Price Discrimination on May 6, and that's the one you added to the DYK nomination page per step 3.
On May 11, you created a second nomination page, Template:Did you know nominations/Gender-based price discrimination. It's this second page that Shubinator's bot picked up on. This second page creation is where you went wrong—it's an unnecessary duplication—and you should add the db-g7 template to it as per the message so it can be deleted. (Don't do anything to the original May 6 page.)
When articles are moved, such as yours was (from Gender-Based Price Discrimination to Gender-based price discrimination, you do not need to create a new nomination page. All you need to do is mention the move on the nomination, and we can make a few adjustments—I've just done that, so your original nomination is up to date as regards naming and links. Please let me know (on my own page; no need to continue this here) if you have any questions or need any further assistance, such as with deleting the May 11 second nominations page. I hope you enjoy the DYK process. BlueMoonset (talk) 13:36, 13 May 2016 (UTC)

DYKUpdateBot missed 12:00 2 June 2016 update[edit]

DYKUpdateBot missed the 12:00 2 June 2016 (UTS) update. There is some maintenance occurring on the Lab servers, but it is not clear from what I can see if the maintenance is of a type that could affect the bot. Please check things when you get a chance. --Allen3 talk 12:27, 2 June 2016 (UTC)

Back up and running! It looks like the bot was confused because {{main page image}} was split across multiple lines -> crash. Thanks for letting me know! Shubinator (talk) 15:09, 2 June 2016 (UTC)

June 12, 2016 DYKUpdate bot didn't clear Queue 2 after putting it on the main page[edit]

I manually cleared the queue about 6 hours later, but the bot missed clearing it. — Maile (talk) 17:53, 12 June 2016 (UTC)

  • The problem of DYKUpdateBot hanging when tagging an image description page repeated during the 00:00 13 June 2016 (UTC) update. The update has been manually completed. --Allen3 talk 00:43, 13 June 2016 (UTC)
    • Thanks both! This is high on my list of things to look into. Shubinator (talk) 14:23, 13 June 2016 (UTC)
  • A repeat of this problem occurred during the 12:00 24 June 2016 (UTC) update. --Allen3 talk 12:08, 24 June 2016 (UTC)

DYKUpdateBot stopped[edit]

Did not do the updates this morning. It seems to have stopped about 12 hours ago. Please fix. — Maile (talk) 12:24, 16 June 2016 (UTC)

I am starting a manual update. --Allen3 talk 12:32, 16 June 2016 (UTC)
Manual update complete. There is no obvious maintenance listed at the Labs-l mailing list, so I am not sure what caused the bot to go MIA. --Allen3 talk 12:46, 16 June 2016 (UTC)
Looks like the bot got snagged in the same bug related to images. The auto-recover code kicked in after the manual update, looks good now. Shubinator (talk) 14:15, 16 June 2016 (UTC)
There seems to still be some type of problem. A test message I placed into User:DYKUpdateBot/Errors has not been cleared despite having been present for a couple of hours. --Allen3 talk 15:05, 16 June 2016 (UTC)
The bot has once again failed to do the 17 June 2016 00:20 (UTC) update just now, so I guess it's nonfunctional at the moment. — Maile (talk) 00:27, 17 June 2016 (UTC)
@Shubinator and Allen3: I just did a manual update. Never having done that before, and not seeing any instructions, I sure hope I did it correctly. — Maile (talk) 00:54, 17 June 2016 (UTC)
My bad, I misread the timestamps in the logs earlier. For some reason the bot's job isn't terminating on the Labs server, which looks like is also preventing me register a new job for the bot. Hopefully in a few hours the job will get cleaned up... Shubinator (talk) 02:23, 17 June 2016 (UTC)
Server still in a bad state, so I'm unable to get the bot running. I can run the bot for a one-off update at ~13:30 UTC. Shubinator (talk) 06:04, 17 June 2016 (UTC)
Thanks to the helpful folks at Tool Labs, DYKUpdateBot is back in action! Shubinator (talk) 06:20, 17 June 2016 (UTC)
It just worked!! Thanks. — Maile (talk) 12:38, 17 June 2016 (UTC)

I think DYKUpdateBot is down[edit]

Shubinator, it doesn't look like DYKUpdateBot finished the last set of updates, though it did the bulk of the work. It didn't clear the queue, and it hasn't promoted the subsequently loaded queue, though that was in place at 08:15, in plenty of time for a 12:05 promotion. Please do what you can to get the bot running as soon as you can, or if it's running, to pick up the waiting queue. Many thanks.

Allen3, is there any chance you can do a manual promotion while we're waiting for the bot to be restarted? Thanks for anything you can do.

Note that Queue 3, the queue that is currently sitting there waiting for promotion, is also the queue that wasn't cleared by the bot (not to worry: this is an entirely new set of hooks, taken from Prep 5). There's been a bit of confusion lately around preps and queues; I'm hoping that things will straighten out going forward. BlueMoonset (talk) 20:34, 25 June 2016‎ (UTC)

Looks like the same bug we've been seeing where the bot chokes on the file :( The bot did auto-recover and appears to be operating normally at the moment. I'll look into the bug when I get the time! Shubinator (talk) 05:14, 27 June 2016 (UTC)
Thanks for checking, Shubinator. BlueMoonset (talk) 06:03, 27 June 2016 (UTC)

User:DYKUpdateBot userpage[edit]

Hello Shubinator, I'm not sure why this bot blanked its own userpage - but as an admin bot we really need to have some information available to people landing on that page, and the categorizations are somewhat useful. If you are retiring this bot please let us know so that it have flags removed. Please let me know if I missed something else that may be going on. — xaosflux Talk 13:01, 1 July 2016 (UTC)

Looks like it's an extremely rare bug, under normal conditions the bot shouldn't be blanking its own userpage. Shubinator (talk) 13:47, 1 July 2016 (UTC)

Bot not clearing queue after promoting[edit]

I just manually cleared Queue 2. The bot updated the main page hooks 20 minutes ago, but did not clear the queue afterwards. — Maile (talk) 14:46, 14 July 2016 (UTC)

Thanks for letting me know! Looks like a repeat of the same bug we've been seeing. Bot is back to normal. Shubinator (talk) 00:58, 15 July 2016 (UTC)

Bot vs Bot[edit]

The FACBot didn't like the dyktalk entries being created by the DYKUpdateBot.

According to the documentation, these should be in the form:

{{DYK talk|date|hook}}

But the DYKUpdateBot is using an undocumented form:

{{DYK talk|day month|year|hook}}

I have changed the FACBot to accept this form. Do we need to update the documentation? Hawkeye7 (talk) 07:56, 20 August 2016 (UTC)

Makes sense to me. DYKUpdateBot is using the same form its predecessors used. Looks like the documentation used to align with the bots, but was changed with this edit, so you may want to double-check with that editor as well. Shubinator (talk) 15:14, 20 August 2016 (UTC)

Updating "DYK is almost overdue" message[edit]

Shubinator, it was just pointed out that the auto-generated overdue message by DYKUpdateBot needs a bit of updating.

Step number 1 currently starts with the admonition Check the prep areas. The problem is that "prep areas" is a hard link to Prep 1, which is not always the next available prep. We now have six preps; the next prep that should be promoted (and is the first one they should check to see whether it has been filled) is recorded at Template:Did you know/Queue/NextPrep (it's an integer from 1 to 6).

The message has been like this for years, but it take new eyes to notice that something doesn't make sense in old boilerplate, and MPJ-DK noticed the discrepancy. I'm guessing it won't be a difficult fix; how soon do you think you'll be able to find some time to update the bot? Thanks, and I hope you're having a great summer. BlueMoonset (talk) 04:12, 25 August 2016 (UTC)

Should be straightforward, I'll try to find time within a week to fix it. Shubinator (talk) 05:17, 26 August 2016 (UTC)
That's great, Shubinator. Thank you so much. BlueMoonset (talk) 22:25, 26 August 2016 (UTC)
Done :) Shubinator (talk) 03:00, 29 August 2016 (UTC)
And again, thanks. I look forward to seeing it soon—but not too soon or too often, since that means we have a queue that needs to be filled pronto, which gets annoying if it happens too frequently. BlueMoonset (talk) 03:32, 29 August 2016 (UTC)

A new draft[edit]

Hey. So there's this new draft I've written at Draft:Devonshire White Paper and I would really like to see it at DYK some time in the future. Would you mind checking it out. Really sorry to bother you like this, but I'm so new to this DYK thing. Thanks, MediaKill13 (talk) 10:50, 30 August 2016 (UTC)

Welcome to DYK! Unfortunately I myself haven't edited or reviewed articles at DYK in a few years, so it's best to ask one of the regulars over at WT:DYK. (Talk page stalkers, if you'd like to help, feel free to chime in.) Shubinator (talk) 00:20, 31 August 2016 (UTC)

August 31 Labs maintenance appears to have halted ‎DYKHousekeepingBot[edit]

There were a couple of maintenance operations performed on the Labs servers today.[1][2] It would appear that one of them took out DYKHousekeepingBot (this addition occurred over an hour ago and the bot has not made an appropriate update). DYKUpdateBot has not had a scheduled update since ‎DYKHousekeepingBot's last update but if we lost one bot then it is likely we lost both. When you get a chance, please check both ‎bots and restart them if needed. --Allen3 talk 21:41, 31 August 2016 (UTC)

Both bots back up and running! Thanks for letting me know :) Shubinator (talk) 01:12, 1 September 2016 (UTC)

Pallache family[edit]

Is the submission for the Pallache family and related articles now correct? (Listed under September 17, 2016) --Aboudaqn (talk) 14:16, 20 September 2016 (UTC)

It looks a little off, for example the ellipses after "that" are unnecessary. Best to ask the folks at WT:DYK to double-check, I've been away from the nominations page for too long to give good advice :) Shubinator (talk) 14:49, 20 September 2016 (UTC)

Extended confirmed protection[edit]

Padlock-blue.svg Hello, Shubinator. This message is intended to notify administrators of important changes to the protection policy.

Extended confirmed protection (also known as "30/500 protection") is a new level of page protection that only allows edits from accounts at least 30 days old and with 500 edits. The automatically assigned "extended confirmed" user right was created for this purpose. The protection level was created following this community discussion with the primary intention of enforcing various arbitration remedies that prohibited editors under the "30 days/500 edits" threshold to edit certain topic areas.

In July and August 2016, a request for comment established consensus for community use of the new protection level. Administrators are authorized to apply extended confirmed protection to combat any form of disruption (e.g. vandalism, sock puppetry, edit warring, etc.) on any topic, subject to the following conditions:

  • Extended confirmed protection may only be used in cases where semi-protection has proven ineffective. It should not be used as a first resort.
  • A bot will post a notification at Wikipedia:Administrators' noticeboard of each use. MusikBot currently does this by updating a report, which is transcluded onto the noticeboard.
Please review the protection policy carefully before using this new level of protection on pages. Thank you.
This message was sent to the administrators' mass message list. To opt-out of future messages, please remove yourself from the list. 17:49, 23 September 2016 (UTC)

DYKUpdateBot didn't do 00:00 1 October 2016 update to main page[edit]

Shubinator, DYKUpdateBot didn't do the daily DYK update at midnight, 1 October 2016, and the update is currently about 4 hours overdue. I hope you'll see this soon and be able to get the bot working again. Thanks!

The DYKHousekeepingBot seems to have survived whatever happened to DYKUpdateBot; it has already done three separate updates today. BlueMoonset (talk) 03:58, 1 October 2016 (UTC)

Looking. Feels like the apostrophe in the next set's filename is confusing the bot. Shubinator (talk) 04:46, 1 October 2016 (UTC)
After unescaping the apostrophe we're back in business :) Thanks for pinging me! Shubinator (talk) 04:49, 1 October 2016 (UTC)
Thanks for responding so quickly! Good to know all is well. BlueMoonset (talk) 06:59, 1 October 2016 (UTC)

Why does the bot it suggest G7?[edit]

I suspect that 99% of the messages DYKHousekeepingBot sends out are due to missing templates on the main nom page, right?

So then why does it suggest G7 as a solution? Oddly, it doesn't suggest anything that will save the nom, only two ways to destroy it.

Maury Markowitz (talk) 12:04, 25 October 2016 (UTC)

The message proposes two different paths forward. If the nominator would like to continue, the message links to the nomination procedure. If the nominator would not like to continue, the message suggests steps to clean up the nomination. Feel free to edit the message, it lives here: Template:DYK nomination needs transcluded. Shubinator (talk) 06:25, 26 October 2016 (UTC)
Should I edit it in place? I do not understand the instructions below. In any event, here is what I would have done:

Symbol question.svg Hello! Your submission of [[]] at the Did You Know nominations page is not complete; if you would like to continue the process, you need to link your nomination page to the main DYK nomination page, see step 3. If you do not want to continue with the nomination, tag the nomination page with {{db-g7}}, or ask a DYK admin. Thank you.

Maury Markowitz (talk) 17:51, 27 October 2016 (UTC)

Thanks! I've gone ahead and updated the message, let me know if it needs further tweaking. Shubinator (talk) 01:05, 28 October 2016 (UTC)

DYKHousekeepingBot is down[edit]

Shubinator, the bot hasn't done any updating since 17:49 UTC on the 25th, over 19 hours ago. There have been a number of events that would have triggered a bot update, including the new day. Thanks for getting it restarted. (DYKUpdateBot seems to be fine; it did the midnight update as usual.) Thanks! BlueMoonset (talk) 13:05, 26 October 2016 (UTC)

Back up and running :) Not sure why it went down in the first place, possibly server maintenance. Thanks for letting me know! Shubinator (talk) 14:10, 26 October 2016 (UTC)
Thank you for getting it back up and running so quickly! BlueMoonset (talk) 04:35, 27 October 2016 (UTC)

DYKUpdateBot is down[edit]

DYKUpdateBot did not update Queue 5 to the main page today. It's about half an hour overdue right now. — Maile (talk) 00:22, 2 November 2016 (UTC)

Restarting... Shubinator (talk) 00:25, 2 November 2016 (UTC)
Thank you. — Maile (talk) 00:30, 2 November 2016 (UTC)
No problem :) Both bots are back up and running. Thanks for pinging me! Shubinator (talk) 00:38, 2 November 2016 (UTC)

DYKHousekeepingBot down?[edit]

Shubinator, I believe that the bot is down; it hasn't updated since 00:10 November 9, and there should definitely have been an update at approximately the same time today (November 10) with the shifting of the dates, but it's 00:47 and the date shift was at 00:04. Thanks for any help you can give. (Note: DYKUpdateBot ran at 00:00 as scheduled, so it's apparently still up.) BlueMoonset (talk) 00:52, 10 November 2016 (UTC)

How odd. Every time DYKHousekeepingBot tries to edit, Wikipedia says it's edit-conflicting. Shubinator (talk) 01:33, 10 November 2016 (UTC)
I'm not sure why Wikipedia thinks the bot is edit-conflicting. It's possible Wikipedia doesn't think the bot is signed in. I can take a longer look over the weekend, unfortunately the bot will be out of commission until this is sorted out. Shubinator (talk) 01:49, 10 November 2016 (UTC)
One of your attempts seems to have worked, though it oddly isn't showing under the DYKHousekeepingBot contributions list: the page says it was updated at 01:28, 10 November 2016 (UTC), but not since. Thanks for the manual run. I hope you don't mind, but I removed that "0" you added, which hadn't managed to provoke an automatic update (and also two empty days, since those dates have been removed). If you can do a manual run once a day until the bot is fixed, at some point after the new day has been added to the nominations page (usually by 00:10), that would be fabulous, but if it isn't convenient, we can certainly continue muddling along. BlueMoonset (talk) 19:20, 10 November 2016 (UTC)
Sure, I'll aim for ~daily manual updates :) Shubinator (talk) 03:52, 11 November 2016 (UTC)
Curious. The bot works when I run it under my account. Shubinator (talk) 23:25, 20 November 2016 (UTC)
Found the issue, bot should be running normally now :) Thanks for your patience! Shubinator (talk) 23:50, 20 November 2016 (UTC)

Two-Factor Authentication now available for admins[edit]

Hello,

Please note that TOTP based two-factor authentication is now available for all administrators. In light of the recent compromised accounts, you are encouraged to add this additional layer of security to your account. It may be enabled on your preferences page in the "User profile" tab under the "Basic information" section. For basic instructions on how to enable two-factor authentication, please see the developing help page for additional information. Important: Be sure to record the two-factor authentication key and the single use keys. If you lose your two factor authentication and do not have the keys, it's possible that your account will not be recoverable. Furthermore, you are encouraged to utilize a unique password and two-factor authentication for the email account associated with your Wikimedia account. This measure will assist in safeguarding your account from malicious password resets. Comments, questions, and concerns may be directed to the thread on the administrators' noticeboard. MediaWiki message delivery (talk) 20:33, 12 November 2016 (UTC)

A new user right for New Page Patrollers[edit]

Hi Shubinator.

A new user group, New Page Reviewer, has been created in a move to greatly improve the standard of new page patrolling. The user right can be granted by any admin at PERM. It is highly recommended that admins look beyond the simple numerical threshold and satisfy themselves that the candidates have the required skills of communication and an advanced knowledge of notability and deletion. Admins are automatically included in this user right.

It is anticipated that this user right will significantly reduce the work load of admins who patrol the performance of the patrollers. However,due to the complexity of the rollout, some rights may have been accorded that may later need to be withdrawn, so some help will still be needed to some extent when discovering wrongly applied deletion tags or inappropriate pages that escape the attention of less experienced reviewers, and above all, hasty and bitey tagging for maintenance. User warnings are available here but very often a friendly custom message works best.

If you have any questions about this user right, don't hesitate to join us at WT:NPR. (Sent to all admins).MediaWiki message delivery (talk) 13:47, 15 November 2016 (UTC)

Update bot is down[edit]

The DYK Update bot has missed the update time. — Maile (talk) 00:21, 16 November 2016 (UTC)

I'm not sure what went wrong; the bot's logs cut off more than a day ago. That said, I've restarted the bot, and it looks normal now. Thanks for letting me know! Shubinator (talk) 02:52, 16 November 2016 (UTC)
Shubinator, whatever you did doesn't seem to have taken; the bot hasn't made an edit since November 15. I'm going to see whether there's anyone around who can do a manual update. Please take another look. Many thanks! BlueMoonset (talk) 00:44, 17 November 2016 (UTC)
It looks the bot process was killed, which is different from whatever happened yesterday. I've started DYKUpdateBot back up again. Shubinator (talk) 02:03, 17 November 2016 (UTC)
Not working again. Is somebody messing with the bot? — Maile (talk) 00:13, 19 November 2016 (UTC)

The bot was fine, just nobody cared to protect the image file of the main hook (and I've missed that too). Materialscientist (talk) 00:38, 19 November 2016 (UTC)

I don't have admin rights on Commons, but it's good information to have. — Maile (talk) 00:41, 19 November 2016 (UTC)
As an admin you can upload the image on en.wiki under the same name and full-protect it here. The image will be deleted later. This is a regular procedure. Materialscientist (talk) 01:22, 19 November 2016 (UTC)
Thank you. So kind of a reverse thing. It's on Commons, but I could upload it as a File on Wikipedia and protect it that way. — Maile (talk) 01:27, 19 November 2016 (UTC)
Yep. For future reference, the bot outputs error messages on User:DYKUpdateBot/Errors for certain errors, like unprotected images. Shubinator (talk) 05:03, 19 November 2016 (UTC)

ArbCom Elections 2016: Voting now open![edit]

Scale of justice 2.svg Hello, Shubinator. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery (talk) 22:08, 21 November 2016 (UTC)

Speedy deletion nomination of File:ThunderII.jpg[edit]

A tag has been placed on File:ThunderII.jpg requesting that it be speedily deleted from Wikipedia. This has been done under section F2 of the criteria for speedy deletion, because it is an image page for a missing or corrupt image or an empty image description page for a Commons-hosted image.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be removed without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. Sfan00 IMG (talk) 10:17, 26 November 2016 (UTC)

DYKUpdateBot didn't complete last night; it might or might not need to be restarted[edit]

Shubinator, last night the DYKUpdateBot died before it did any of the notifications; basically, it updated the main page, archived the old set, and set the time for the next update. That's it. It didn't to the notifications, and more crucially it didn't clear out Queue 1 or update the next queue to be Queue 2.

I've put out a call for an admin to reset the next queue to 2 and to empty out Queue 1, as well as do all the uncompleted notifications to article talk pages and user talk pages, but in case you're around, I was hoping you could keep an eye on the bot and make sure it started up again at midnight UTC. Many thanks. BlueMoonset (talk) 20:00, 16 December 2016 (UTC)

Shubinator, I just did a manual update. The DYKUpdateBot is still not running. — Maile (talk) 00:36, 17 December 2016 (UTC)
I've restarted the bot. It looks like User talk:Samuele Madini is an edge case that hit a bug in the bot - it's a user talk page that redirects to a non-talk page. Shubinator (talk) 03:11, 17 December 2016 (UTC)

https://en.m.wikipedia.org/wiki/Wikipedia:Recent_additions Is not updated.

06:24, 17 December 2016 (UTC)  — Preceding unsigned comment added by 46.39.230.243 (talk)  
Good call, I've updated it with the 17 December set :) Thanks! Shubinator (talk) 01:13, 19 December 2016 (UTC)

Possible changes to the DYK nominations page and DYKHousekeepingBot[edit]

Shubinator, the problems we were having with the DYK nominations page (T:TDYK) not being able to transclude all of the nominations has been recurring since the end of November, and getting steadily worse. I think it's now attributable to the overall increase in template usage in individual nominations—it's now a rare one that doesn't use the ping template, for example—and the increasing number of extant nominations.

While a number of suggestions were bruited about in the most recent DYK talk-page discussion, including when to close nominations and the like, it seems like the one that received general support is the one to split the nomination page into two pages: one for nominations still needing approval (Regular), and one for approved nominations (Approved).

It seemed to me that this split would require changes to the DYKHousekeepingBot:

  • To build the List of DYK Hooks by Date table that's currently included on the Queues and Preps and Nominations pages, it would need to check and extract data from both the existing Regular nominations page and the new Approved nominations page.
  • Ideally, the bot would also take any nominations on the Regular nominations page that have been approved and move them to the Approved nominations page.
  • Also, the bot would take any nominations from the Approved nominations page that have run into trouble, and move them back to the Regular nominations page.

However, I imagine that the code to move hooks from one page to another could take some time: new date sections might need to be created as part of a move, for example. You'd also need to protect against editing collisions: people adding new template transclusions to the Regular page, moving hooks to the Special Occasions section (which would be located on the Approved page), and the bot adding a new day and rotating the New section of the Regular page, which happens once daily. Also, I rather suspect some people will move hooks by hand between pages rather than wait for the bot to do it.

So, the big question would seem to be whether you have time to take on this project, and how long each phase would take. The crucial one is the first one: getting the DYKHousekeepingBot to be able to read and combine the data from the Regular and Approved pages into a single table. Once that is ready, we can go live with it and manually move the hooks between the Regular and Approved pages. (It will be a bit of a pain, but at least all nominations will once again be visible.)

I suppose, technically, we could set up the Approved page and just have the hooks moved there disappear from the Nominated page, while you're working on the code for the List of DYK Hooks by Date; I think it would be confusing to have them just disappear, though. Do you have a suggestion on a name for the Approved page? Or should we put it directly "below" the nominations page: Template talk:Did you know/Approved?

Thanks for any advice you can give, and your thoughts about how long it would take to revise the bot for each of these steps. BlueMoonset (talk) 20:08, 17 December 2016 (UTC)

I can get the first step up and running later this week. Would be great if someone could create the Approved page with one or two (possibly fake) noms so I have something to work off of. Template talk:Did you know/Approved works for me :) I should have time this Friday, so if the Approved page is created before Dec 23 00:00 UTC, I can likely get the bot reading both pages by Dec 24 00:00 UTC.
As you mentioned, moving the nominations around is likely to cause edit conflicts, and right now neither bot handles edit conflicts gracefully, so it might best for the bots to not do these tasks. Shubinator (talk) 01:08, 19 December 2016 (UTC)
Shubinator, I imagine that any moving will be done by the bot Wugapodes will be building, so we'll let him worry about that when the time comes.
In the meantime, I have just created the Approved page. Sorry it's a day later than you were hoping. Based on the most recent discussion at DYK talk, it seems clear that this page will not be date based; while it may have sections, I think for the time being you should ignore the possibility and just list/count all of the hooks regardless of section (yes, including the special occasion ones).
I've structured the page with an overall first-level Nominations section like the current Nominations page, and second-level "Approved nominations" and "Special occasion holding area". However, while the Special occasion second has third-level headers (by date), the Approved nominations section does not. Will your bot look up and count the nominations in both sections even if they're at different levels, or would it be better to put in a third-level header under Approved nominations (called, say, "Ready for promotion")? Also, it seems to me that since there won't be any dates on the Approved page, would it make sense to give the page its own line on the "List of DYK Hooks by Date" table, and perhaps (because there won't be dates there) rename the table?
I should mention that it is possible for hooks to be on the Approved page and not be approved, since subsequent reviewers can come in and find issues with them, so there may be more total hooks than verified hooks.
I stocked the Approvals page with four approved but unpromoted hooks. (They're all from December 6 on the Nominations page.) There are also three approved hooks in the Special occasions section; I basically duplicated everything there that hadn't been promoted, all of which were from the New Year.
Please let me know if you have any questions or preferences, or would like adjustments to the newly created Approvals page. Many thanks! BlueMoonset (talk) 00:01, 24 December 2016 (UTC)
Thanks! As long as each nomination has a fourth-level header, the bot will be able to parse it out. For the table, is something like this what you were thinking?
Count of DYK Hooks
Section # of Hooks # Verified
December 14 6 4
December 15 8 2
December 16 14 4
December 17 10 7
Approved 4 3
Total 42 20
Last updated 01:05, December 24, 2016 (UTC)
Current time is 02:15, 27 March 2017 UTC [refresh]
Shubinator (talk) 01:06, 24 December 2016 (UTC)
Shubinator, thank you. Yes, that was what I was thinking of. It's good to know about the fourth-level headers; since all nomination templates are built with those headers, then we should be all set—I'm guessing that it doesn't matter whether the structure above them includes third-level headers or not. Can I make a minor request regarding the dates at the bottom of table? It's always seemed odd to me that the "Last updated" line uses an mdy date, while the "Current time" uses the dmy format. Any chance that they could standardize? (I'd imagine dmy should be used if so, since it's what we get in edit histories and user contribution pages and the like.) Once you have a test version ready, some input from the others would make sense: would "Approved" or "Approved page" be clearer, should it have a white background or pink or another color, and so on. The page will eventually need to change again once the other features have been nailed down and implemented, but this allows the two-page solution to be implemented. BlueMoonset (talk) 15:10, 24 December 2016 (UTC)
Done :) See the bot's output here: User:Shubinator/Sandbox/DYK hook count. If the discussion settles on date sections for the Approved page, it's relatively easy to tweak the bot code for date sections in the future. Shubinator (talk) 23:38, 24 December 2016 (UTC)
The bot version currently being tested (you've just been pinged from one of the discussion pages) has date sections for the Approved page, so it would be nice if you'd tweak your bot code in that direction. It has been pointed out, however, that the links do go to the Nominations page, which isn't helpful if you're working on the Approved page. Right now, the links work differently depending on whether you're on the Queues page or the Nominations page. How feasible would a three-way test/formation be when adding the Approved page into the mix? I'm guessing it's more complicated, and not only because both Nominations and Approved pages have the same top-level directory... BlueMoonset (talk) 16:34, 20 January 2017 (UTC)
I'll try to make the change within a week. Tweaking the links to support the Approved page should be doable, the table would always link to sections within the Approved page if it detected it was on the Approved page. Shubinator (talk) 05:39, 23 January 2017 (UTC)
Done, check out User:Shubinator/Sandbox/DYK hook count. The table reflects unapproved + approved hooks on both the normal nominations page (User:Wugapodes/DYKTest) and the approved page (User:Wugapodes/DYKTest/Approved). Links are formatted as described above; the table links to sections within the Approved page if it thinks it's on the Approved page. Shubinator (talk) 01:56, 30 January 2017 (UTC)
I've updated the live version of DYKHousekeepingBot with the above changes, so it now picks up nominations on the Approved page that are in date sections. Hopefully everything will work seamlessly when Wugapodes's bot is started up. Shubinator (talk) 05:29, 5 February 2017 (UTC)
Thanks, Shubinator; it looks good! Wugapodes has just posted that the power and wifi are both out due to a storm, so the Wugbot runs are delayed by a day. BlueMoonset (talk) 06:49, 5 February 2017 (UTC)

Recent DYKUpdateBot issues[edit]

Shubinator, DYKUpdateBot has recently had some trouble with completing its updates. Today's 12:00 update that moved Queue 3 to the main page stopped after posting the notifications to the editors (the DYKmakes and DYKnoms) and before adding the credit to the image page. The same thing happened with Queue 1 36 hours earlier (we've just gone from updates every 24 hours to updates every 12 hours).

The problem with the update dying on the image step is that the key final steps—clearing the queue and updating "next" to the next queue—don't get done. And there isn't always an admin around, which could mean a queue getting promoted again if a clean-up isn't done.

Is there a way of making the image credit step more bulletproof—that is, if something goes wrong, can it just proceed without doing the credit? And if that's going to continue to be problematic—these are hardly the only times the image credit step has failed and caused this problem—might it make sense to swap the order of steps so the image credit is done last, after emptying the queue and updating to the next one? (You'd need to keep the image data around after the queue holding it was gone.) Sometimes it does manage to fail over: on January 8, while the image credit isn't logged, after a four minute gap the bot was able to finish up. January 9, as noted above (Queue 1), there was no recovery and the bot didn't do those all-important final steps.

Thanks for anything you can do. Please let me know what you think is feasible. BlueMoonset (talk) 18:32, 10 January 2017 (UTC)

Looks like a couple different things are happening. First, DYKUpdateBot's delete and unprotect abilities appear to be broken. I'm not particularly surprised, a year ago I suspected the quick patch implemented here fixed edit capabilities but not delete/protect/etc. Thankfully DYKUpdateBot only uses delete/unprotect for image related stuff, nothing crucial to the updates. A year ago DYK was rarely uploading temporary files to English Wikipedia so I didn't get a chance to test my hunch at the time. Second, for some reason the bot is having trouble editing images that were once on English Wikipedia but have since moved to Commons. Not sure why.
As for solutions. I've gone ahead and commented out the code for deleting/unprotecting files as they come off the Main Page. I've moved the image-related part of the update to the very end as you suggested. And I've also fixed the edge case that took down the bot last month. The code change is here for the curious.
Do we think the delete/unprotect functionality is valuable? I'm not sure how much effort it would take to fix this. If we want to fix it, I may just rewrite the bot against pywikibot (which has a healthy community of bots using it) instead of making my own fixes to the 8-year-old JavaWikiBotFramework (which has pretty much no community, and no updates in years). That said, I'm not sure when I'll find the time to rewrite our beloved bot.
As always, thanks for letting me know of trouble brewing. Shubinator (talk) 05:51, 12 January 2017 (UTC)

DYKUpdateBot appears to be down[edit]

Shubinator, the bot didn't run at 22:07 30 January 2017 like it should have; it's now 00:13 31 January 2017 and no sign of the bot doing as it ought. Can you please restart it as soon as you see this? Many thanks. PS: I'll let you know if I hear more from Wugapodes on progress. In the meantime, we've finally got all of the hooks visible again on the Nominations page, though I have no idea how long that will last. BlueMoonset (talk) 00:14, 31 January 2017 (UTC)

Materialscientist did a manual update, so we're set for the next half day: the next update is scheduled for shortly after noon UTC. Still, I'm hoping you see this well before then and can give DYKUpdateBot a restart. Note that DYKHousekeepingBot seems to be working fine; it last updated about 40 minutes ago, to reflect the new date added to the Nominations page shortly after midnight. BlueMoonset (talk) 00:50, 31 January 2017 (UTC)
I've restarted the bot. I'm not sure what went wrong, the bot's output stops on Jan 19th. Hopefully if/when it happens again, the logs will capture whatever it is. Thanks for letting me know! Shubinator (talk) 02:08, 31 January 2017 (UTC)

Administrators' newsletter - February 2017[edit]

News and updates for administrators from the past month (January 2017). This first issue is being sent out to all administrators, if you wish to keep receiving it please subscribe. Your feedback is welcomed.

Admin mop.PNG Administrator changes

Gnome-colors-list-add.svg NinjaRobotPirateSchwede66K6kaEaldgythFerretCyberpower678Mz7PrimefacDodger67
Gnome-colors-list-remove.svg BriangottsJeremyABU Rob13

Green check.svg Guideline and policy news

Octicons-tools.svg Technical news

  • When performing some administrative actions the reason field briefly gave suggestions as text was typed. This change has since been reverted so that issues with the implementation can be addressed. (T34950)
  • Following the latest RfC concluding that Pending Changes 2 should not be used on the English Wikipedia, an RfC closed with consensus to remove the options for using it from the page protection interface, a change which has now been made. (T156448)
  • The Foundation has announced a new community health initiative to combat harassment. This should bring numerous improvements to tools for admins and CheckUsers in 2017.

Scale of justice 2.svg Arbitration

Nuvola apps knewsticker.png Obituaries

  • JohnCD (John Cameron Deas) passed away on 30 December 2016. John began editing Wikipedia seriously during 2007 and became an administrator in November 2009.

13:37, 1 February 2017 (UTC)

DYK bot difficulty again[edit]

@Shubinator and BlueMoonset: When the bot swapped out the sets at 00:00, 11 February 2017, it did nothing else, it did not place the DYK templates on the individual pages. Even though it also missed the update at 12:00 today, there was no message on WT:DYK that the update was late. I manually did the update and reset the clock according to the instructions on its page. I also did a manual update of Wikipedia:Recent additions. — Maile (talk) 12:50, 11 February 2017 (UTC)

@Shubinator and BlueMoonset: I don't know where you are, but the bot is nowhere right now. Second manual update in a row. — Maile (talk) 01:11, 12 February 2017 (UTC)
Thanks! Looks like the bot ran out of memory (which is unusual), so it crashed. I've restarted the bot and it's back to normal now. Shubinator (talk) 02:42, 12 February 2017 (UTC)

Can you run the untranscluded DYK nomination templates list?[edit]

Shubinator, it might be nice to have this list run again now, while the nominations are comparatively recent. Thanks. BlueMoonset (talk) 17:48, 4 March 2017 (UTC)

Sure, I've put the list at Wikipedia talk:Did you know#Orphaned nominations March 2017. Shubinator (talk) 07:44, 5 March 2017 (UTC)
Thanks. I expected a bit more than that, but it's good to get these done. BlueMoonset (talk) 08:29, 5 March 2017 (UTC)
No problem :) My part was easy, thanks for looking at them individually! Shubinator (talk) 23:53, 5 March 2017 (UTC)

DYKHousekeepingBot is down[edit]

Shubinator, the bot last ran at 16:25 today. Since then, there have been a few new hooks added, none promoted that I'm aware of, plus I created a new date (March 6) for a badly misplaced hook at 23:13 which hasn't yet resulted in a DYKHousekeepingBot update, although that was 35 minutes ago. I'm forced to conclude that the bot is not currently running, and needs manual intervention on your part. Thanks as always for your help and your bots. BlueMoonset (talk) 23:49, 20 March 2017 (UTC)

Restarted, it's back up and running now. Not sure what happened, the bot's process was no longer running but the logs don't show anything unusual. Thanks for pinging me! Shubinator (talk) 03:18, 21 March 2017 (UTC)
Thanks for getting it back up and running! BlueMoonset (talk) 17:25, 21 March 2017 (UTC)

DYKUpdateBot missed 25 March 2017 00:00 update, but don't restart it unless the next update time has been updated[edit]

Shubinator, in case you didn't see the ping from the WT:DYK page, DYKUpdateBot didn't run when it was supposed to about three and a half hours ago (its last edit was at 00:02 on 24 March 2017 (UTC), and a partial manual update was done about 50 minutes later that failed to include updating the time of the next update, but did include incrementing the next queue to be promoted. Please do not restart the bot until first making sure that Template:Did you know/Next update/Time has been updated from 2017-03-24T00:00:00Z to 2017-03-25T00:00:00Z ("24" needs to have been changed to "25"); otherwise, the bot will immediately overwrite the set that was manually updated with a new queue, which would be bad. BlueMoonset (talk) 04:15, 25 March 2017 (UTC)

I've completed the latest manual update, so the only problem is to revive the bot. Materialscientist (talk) 05:52, 25 March 2017 (UTC)
Thanks both! I've started the bot back up. At a glance the logs show the bot crashed in the image protection logic, my hunch is the nested template on that set confused the bot. Shubinator (talk) 06:14, 25 March 2017 (UTC)