User talk:Shubinator/Archive 44

User

Talk

Scripts, Templates, & Bots

Contributions

Email

Awards

Archive 40

←

Archive 42

Archive 43

Archive 44

Archive 45

Archive 46

→

Archive 50

Bot is down

It appears the DYK housekeeping bot has been down for the last 36 hours or so. --ThaddeusB (talk) 21:15, 17 May 2015 (UTC)

Back up and running, thanks for pinging me! Shubinator (talk) 22:21, 17 May 2015 (UTC)

DYKcheck bookmarklet

Hi. I tried DYKcheck using the address bar url snippet from Did you know/DYKcheck, but nothing seemed to happen. I did try bypassing the cache; no joy though. I wondered if you might take a look at it? The prosesize scripts …Dr pda/prosesizebytes.js'); getDocumentSize(); worked fine. Thanks, Shubinator. 146.199.151.33 (talk) 04:06, 28 May 2015 (UTC)

Looks like both prosesize and DYKcheck work in Internet Explorer using this route, but neither work in Firefox. Honestly I'm a bit surprised it works at all, this used to consistently work but broke a while back. Which browser + version are you using? Shubinator (talk) 04:50, 28 May 2015 (UTC)

Sorry, I think this is my fault; I wrapped the whole script in a function, which meant that the dykCheck function wasn't exposed globally any more. This edit should take care of that particular issue. 146.199.151.33, could you try it again and see if it works? — Mr. Stradivarius ^{♪ talk ♪} 05:00, 28 May 2015 (UTC)

That fixed it, thank you! I'd tried it in a few browsers, Firefox v. 29 & then 38. dykcheck as well as prosesize now work. I need to enter the lines via the developer console rather than the address bar in Firefox or IE 11 (although Pale Moon 25.4x is happy with the address bar), which is down to the browsers, but that's fine with me. –146.199.151.33 (talk) 20:59, 28 May 2015 (UTC)

Bots

You are receiving this message because a technical change may affect a bot, gadget, or user script you have been using. The breaking change involves API calls. This change has been planned for two years. The WMF will start making this change on 30 June 2015. A partial list of affected bots can be seen here: https://lists.wikimedia.org/pipermail/wikitech-l/2015-June/081931.html This includes all bots that are using pywikibot compat. Some of these bots have already been fixed. However, if you write user scripts or operate a bot that uses the API, then you should check your code, to make sure that it will not break.

What, exactly, is breaking? The "default continuation mode" for action=query requests to api.php will be changing to be easier for new coders to use correctly. To find out whether your script or bot may be affected, then search the source code (including any frameworks or libraries) for the string "query-continue". If that is not present, then the script or bot is not affected. In a few cases, the code will be present but not used. In that case, the script or bot will continue working.

This change will be part of 1.26wmf12. It will be deployed to test wikis (including mediawiki.org) on 30 June, to non-Wikipedias (such as Wiktionary) on 1 July, and to all Wikipedias on 2 July 2015.

If your bot or script is receiving the warning about this upcoming change (as seen at https://www.mediawiki.org/w/api.php?action=query&list=allpages ), it's time to fix your code!

• The simple solution is to simply include the "rawcontinue" parameter with your request to continue receiving the raw continuation data (example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&rawcontinue=1>). No other code changes should be necessary.
• Or you could update your code to use the simplified continuation documented at https://www.mediawiki.org/wiki/API:Query#Continuing_queries (example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&continue=>), which is much easier for clients to implement correctly.

Either of the above solutions may be tested immediately, you'll know it works because you stop seeing the warning.

Do you need help with your own bot or script? Ask questions in e-mail on the mediawiki-api or wikitech-l mailing lists. Volunteers at m:Tech or w:en:WP:Village pump (technical) or w:en:Wikipedia:Bot owners' noticeboard may also be able to help you.

Are you using someone else's gadgets or user scripts? Most scripts are not affected. To find out if a script you use needs to be updated, then post a note at the discussion page for the gadget or the talk page of the user who originally made the script. Whatamidoing (WMF) (talk) 19:03, 17 June 2015 (UTC)

Bots are down

Shubinator, DYKUpdateBot's last edit was at 15:08 yesterday, after completing a queue-to-main page update; it should have promoted the next queue 90 minutes ago, and hasn't. DYKHousekeepingBot last updated the table of outstanding hooks by date and approval at 00:17 today, and there have definitely been many changes since then (the most recent hook added at T:TDYK was at 02:22). I hope you see this soon, and can get the bots working again without much difficulty. Many thanks! BlueMoonset (talk) 04:22, 18 June 2015 (UTC)

Thanks for letting me know. Labs is letting me log into the central Labs servers, but the servers specific to Tool Labs aren't recognizing me for some reason. Not sure if the bots' Tool Labs accounts got revoked. I'm traveling at the moment, I'll poke around, will be able to put more time into this on Sunday. Shubinator (talk) 16:11, 18 June 2015 (UTC)

Oh. Looks like Labs is dealing with systemwide filesystem issues today. Once Labs resolves this I can power up the bots. The right Labs folks are working hard to fix it. Shubinator (talk) 16:15, 18 June 2015 (UTC)

Thanks for checking. I guess we'll have to wait for Labs to get things functioning again. Hope it's soon! BlueMoonset (talk) 16:39, 18 June 2015 (UTC)

Both bots back to normal :) Shubinator (talk) 22:56, 19 June 2015 (UTC)

Great! Such a relief. :-) BlueMoonset (talk) 02:49, 20 June 2015 (UTC)