Scrum of scrums/2016-02-24




  • Blocking: (nobody we know)
  • Blocked: (on nothing)
  • Updates:
    • Upgraded to CDH 5.5, comes with lots of improvements for those using the Hadoop cluster:
    • Internally released data that estimates the number of Unique Devices hitting each of our domains, using the Last Access cookie. This is a major release, and it's available in the wmf database in hive, in the last_access_uniques_daily table.
    • Fixed handling of uri-encoded page titles in the pageview API

Release EngineeringEdit

  • Blocking:
  • Blocked:
    • None
  • Updates:
    • AQS deployed via Scap3, (hooray \o/ +1) ready for new services w/new version
    • Phabricator updates happened, puppet work continues
    • Train (still) not running wmf.14 on testwiki and that's all


  • Blocking:
    • nothing we know of
  • Blocked:
    • blocked on ops for ORES in production
      • also blocks deployment of ORES extension to fawiki and wikidata
      • halfak would like to engage with ops - could someone contact him?
  • Updates:
    • none


  • Blocking:
    • ???
  • Blocked:
    • ???
  • Updates:
    • Working through lots of security bugs
    • PageViewInfo review in progress




    • Pageview API graphs getting popular





  • Blocking:
    • None known.
  • Blocked:
    • Waiting on Design Research availability for user testing of Single Edit Tab integration
  • Updates:
    • Single Edit Tab went to Hungarian Wikipedia yesterday; now waiting on user feedback.
    • Some improvements to OOUI; note the breaking change for wmf.15+ (no known issues in gerrit master code).
    • Last week we said we'd update on assessing the performance impact of OOUI on all read pages; this is not firm yet, but appears to be a trivial additional cost.

Fundraising TechEdit

  • No blockers/blocking
  • Investigating anomalies
  • Improving CiviCRM reporting
  • Testing backup processor improvements
  • Further Latin America processor work



  • Updates:
    • Nothing to report.

Reading InfrastructureEdit

  • We've been mostly chasing performance issues that people found that touch stuff SessionManager also touched.
  • In the not too distant future, load.php is going to start enforcing the fact that it's supposed to not depend on the session or the request data.
    • See and subtasks.
    • Check your ResourceLoaderModule subclasses and your 'ResourceLoaderGetConfigVars' hook functions to make sure you're not using $wgUser or $wgLang (or their equivalents via RequestContext). You'll generally want to use the user and language from the ResourceLoaderContext or use the 'MakeGlobalVariablesScript' hook instead. Remember that Message objects will use $wgLang by default.
    • Check your parser hooks to make sure you're using $parserOptions->getUser() or $parser->getTargetLanguage() instead of $wgUser or $wgLang (or their equivalents via RequestContext), respectively. Otherwise you're liable to blow things up if your hook gets used in a message somewhere.
    • Timo says he'll send an announcement of some sort once details are settled.