Since our current Squid stats  don't look very accurate or precise, I
decided to generate something myself based on the logs we have. I
analyzed a week's worth of logs, from 2013-06-10 to 2013-06-16. I
generated three sets of data:
* minor: browsers grouped by their minor version, e.g. all Androids 4.2
go together, all Safaris 5.1, etc.
* major: browsers grouped by their major version, e.g. all Androids 4 go
together, all Safaris 5, etc.
* vendor: browsers grouped by their name only, e.g. all Androids go
together, all Safaris, etc.
Each group has also an additional file with all the unknown user agents
logged (they are logged as "Other" in the main files). Everything is
Most of it looks like I expected, the market is shared mostly among
mobile Safari and Android. What I hadn't expected is that Android 2.3 is
still the most popular Android at 9.79%. That's a lot. I started
thinking what we could do about this. After some googling I found lots
of Android 2.x users frustrated by the fact that Chrome is not available
for Android older than 4 and they're stuck with a crappy browser.
I tried looking for an alternative and I found it rather quickly:
Firefox. Mobile Firefox is a sad 0.26% of our users, even less than
desktop Firefox (0.29%)! I tried installing it on the first Google Nexus
and hey, maybe it's not superfast, but it's better than the stock
Android 2.3 browser and supports both photo uploading and our new editor
really well (stock Android 2.3 doesn't support uploads and the editor
is... quite wonky). So, my suggestion is: let's show a banner or a call
to action for Android 2.x users telling them about this and encouraging
them to try Firefox. It's free open software and I think it's better
than what stock Android 2.x browser is. What do you think? Wikimedia
Foundation <3 Mozilla Foundation? ;)
Unrecognized browsers are mostly bots with one notable exception,
NativeHost, which is probably the Windows Phone app (I'm guessing ).
Jenkins is now blowing up for reasons unknown to me.
Desktop QUnit tests are failing all the time due to timeout reasons (I
can sometimes replicate this locally - this might have been due to
some core change?)
Mobile tests are sometimes passing and sometimes throwing errors due
to no tests being run. See this commit for an example when the mobile
tests passed but core changes failed:
and here where both sets of test failed:
This all started since the seemingly harmless
https://gerrit.wikimedia.org/r/92804 got merged.
any ideas what is going on? This currently stops us merging any code
(since we disabled the verified override)
Also today around 4pm, when wikipedias got switched to 1.23wmf1, the
exception was being thrown due to what I think was some old code being
loaded (when debug=true was appended this error didn't occur so I
suspect some caching issues). Reedy seems to have fixed it with lots
of file touching (thanks Reedy)! Greg, what can we do to avoid this
Everyone, I apologize for the bug.
I'll look for ways to guard better against this risk in the future, which
will be important as we look to expand coverage of Wikipedia Zero to sister
projects and the desktop form factor.
Thanks to everyone for resolving the issue so quickly. You guys rule.
And Roan, thanks for not flipping over my desk, despite the bug making RL
go haywire on Wikidata AND holding up your lightning deployment. It's true
- you are a gentleman and a scholar.
On Wed, Oct 30, 2013 at 5:57 PM, Yuri Astrakhan <yastrakhan(a)wikimedia.org>wrote:
> == Background ==
> ZeroRatedMobileAccess has always depended on MobileFrontend and used it
> liberally, including calls to its classes. However, it was done in hooks
> called by MF so Zero simply stopped working in absence of MF. This,
> however, changed in  where Zero started using a ResourceLoader module
> from MF.
> == What happened ==
> At 23:02pm UTC, after deploying Zero extension updates, fatal monitor was
> flooded with:
> -- Fatal error: Class 'MFResourceLoaderModule' not found in /usr/local/
> line 408
> The issue was tracked down to Wikidata having MobileFrontend disabled,
> while ZeroRatedMobileAccess was enabled. It didn't impact page views
> directly, however all load.php calls that requested the startup module
> caused fatals because it attempted to instantiate MFResourceLoader class
> and couldn't find it. As a consequence, people might have seen pages
> without styles or scripts.
> A number of people (MaxSem, Reedy, Roan, and Greg, and possibly others)
> gave great assistance to track down the issue and rapidly disable the
> ZeroRatedMobileAccess extension in Wikidata. Furthermore, mobile
> configuration  will add an additional guard against calling
> ZeroRatedMobileAccess.php unless it's explicitly within the context of MF.
> Thank you to everyone!!!
> == Timeline ==
> All times in UTC
> * 22:48 Zero 1.22wmf22 deployed, no errors
> * 23:02 Zero 1.23wmf1 deployed, first errors appear - initially unnoticed
> * 23:08 A small MobileFrontend change deployed
> * 23:09 Errors noticed, initially linked with MobileFrontend push
> * 23:17 Max reverts his MobileFrontend changes, errors don't go away
> * 23:22 Problem narrowed down
> * 23:27 Fix deployed
> == Recomendations ==
> * Allow a bit more time between deployments and observe fatalmonitor before
> and after
> * Ensure Zero extension checks if Mobile extension is loaded before
> enabling itself if it relies on MFResourceLoader.
>  https://gerrit.wikimedia.org/r/#/c/83133
>  https://gerrit.wikimedia.org/r/#/c/92811
> Wikitech-l mailing list
Google Code-In is a contest to introduce pre-university students (ages
13-17) to the many kinds of contributions that make open source software
development possible. Students must complete tasks (see examples), one
at a time. The Google Code-in 2013 contest runs from November 18, 2013
to January 6, 2014.
In theory, this program could be very useful to fix little bugs and
implement little features (or bigger, if we know how to split the
tasks), especially in those mobile projects that don't get the top
priority. I have been told by Google and various organization
participanting in the past that Android development is one of strongest
skills among Code-in participants, with iOS and mobile web development
scoring also pretty well.
What do you think?
We are currently preparing the proposal to apply by Oct 28, next Monday.
If you can add at least 5 tasks to the wiki page linked above then you
will be ready for the next level - if we are one of the organizations
selected on November 1.
If you have questions just ask, here or at the related talk page.
Technical Contributor Coordinator @ Wikimedia Foundation
What does the message mobile-frontend-profile-heading-recent refer to? The
qqq documentation doesn't make it so clear, and it doesn't seem to be used
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
“We're living in pieces,
I want to live in peace.” – T. Moore