Bugs, Repairs, and Internal Operational News

Note from the editor: the issue of the Signpost in a fortnight's time will be the first anniversary of my time in the role of "Technology Report" lead. In that time, the flavour of the report has not changed greatly: it is much as it ever was. I would like the 6 June issue to include a handful of trial elements, to see if they meet with approval; as such, it would be great to take comments on this issue about what you, Signpost readers, think about the "Technology Report" and what suggestions you may have. Thank you.

Periods of intermittent slowness (many causing timeouts and consequently edits being lost) intensified this week, prompting a raft of complaints at the English Wikipedia's Technical Village Pump (permalink). The issues were raised on the Foundation's mailing list, prompting WMF Deputy Director Erik Möller to relay suggestions from the Wikimedia operations team as to what might be behind the issues, which have affected users as far apart as the east coast of the United States and Australia:

(The extension deployed on May 18 - cf. bug #21919 - was GoogleNewsSitemap, an extension designed to make wikis, in this case the English Wikinews site, more accessible to the Google News aggregation service.) The problems underline the need for the forthcoming Ashburn, Virginia data centre, through which requests could be rerouted. In his email, Möller also warned against checking the usual reports on Wikimedia uptime at http://ganglia.wikimedia.org, which is "in the process of being fixed".

In unrelated news, this week also saw a fatal error which made Wikimedia Commons unable to accept edits for a period of some minutes (bug #29078).

Not all fixes may have gone live to WMF sites at the time of writing; some may not be scheduled to go live for many weeks.

• The Foundation has announced a "Scheduled intermittent downtime on all Wikimedia projects on May 24" between 13:00 and 14:00 (UTC).
• Wikipedian Tom Morris blogged about his attempts to make Wikipedia more usable on iPads.
• Wikimedia's copy of "phpUnderControl", an automated test suite capable of testing every revision to the MediaWiki software as they come in, was made usable once more by excluding tests that take a long time to run (example of Cruise Control in action). The aim is to be able to find and act on deficiencies in code additions more swiftly than has previously been the case (wikitech-l mailing list).
• At the "GLAMCampNYC" (a meeting of Wikimedians and representatives of "GLAMs", i.e. cultural institutions, see this week's "News and notes"), Sumana Harihareswara wrote about developers' efforts to facilitate such collaboration projects, specifically a tool for mass upload of audiovisual media and for analysis of their usage (Wikimedia Technology blog).
• With the resolution of bug #20699, the API (machine readable) version of the watchlist now includes the log events included on the normal version of the page.
• The CLDR extension was deployed to Wikimedia wikis (bug #28176). It allows for language names to be translated into other languages straight from a Unicode repository when they are not already defined in MediaWiki's own lists.
• Gerard Meijssen blogged about how templates like {{lang-xx}} could be used as a conduit for custom "web" fonts, and the pitfalls in doing so.
• Tables of contents are now no longer displayed on Wikimedia's "Print/export" output (revision #88502).
• IBM developerWorks published an article describing how to "Hook into Wikipedia information using PHP and the MediaWiki API".

← Previous "Technology report"

Next "Technology report" →

In this issue

23 May 2011 (all comments)

News and notes

In the news

WikiProject report

Featured content

Arbitration report

Technology report

+ Add a comment

Discuss this story

These comments are automatically transcluded from this article's talk page. To follow comments, add the page to your watchlist. If your comment has not appeared here, you can try purging the cache.

• Nice to hear about the CLDR extension, but how can it be used? It seems to have only server-side hooks, but it'd be nice to be able to use it in a parser function, such as #languagename (provided by Extension:I18nTags) --Waldir ^talk 03:12, 24 May 2011 (UTC)[reply]
  • Yes, a parser function for accessing the CLDR data would be a very good idea. Kaldari (talk) 06:43, 24 May 2011 (UTC)[reply]

• Regarding the timeouts, I notice that they are more frequent in my preferred browser (Firefox). When I am experiencing one, I can often be productive in an alternative browser such as Chrome.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 16:49, 24 May 2011 (UTC)[reply]