User talk:Shubinator/Archive 48

User

Talk

Scripts, Templates, & Bots

Contributions

Email

Awards

Archive 45

Archive 46

Archive 47

Archive 48

Archive 49

Archive 50

→

Archive 55

Issues with DYKcheck?

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

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

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

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.
  • Fixed! Shubinator (talk) 00:21, 18 January 2016 (UTC)
• 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.
  • Fixed! Shubinator (talk) 00:21, 18 January 2016 (UTC)

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?

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

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.

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

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

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

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)

Took four years, but this is now fixed :) see the "Count of DYK Hooks page error" section. Shubinator (talk) 17:08, 10 March 2020 (UTC)

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

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

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)

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

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

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

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

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

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

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)