This might be interesting, as moving from Ruby to Node.js is one of our
quarterly goals. :)
Product Manager, Discovery
---------- Forwarded message ----------
From: Željko Filipin <zfilipin(a)wikimedia.org>
Date: Thu, Oct 26, 2017 at 11:59 AM
Subject: [Engineering] Tech talk: Selenium tests in Node.js
To: "Software quality assurance for Wikimedia projects." <
qa(a)lists.wikimedia.org>, Development and Operations Engineers <
engineering(a)lists.wikimedia.org>, Wikimedia developers <
# Who 👨💻
Željko Filipin, Engineer (Contractor) from Release Engineering team. That's
# What 📆
Selenium tests in Node.js. We will write a new simple test for a MediaWiki
extension. An example: https://www.mediawiki.org/wiki/Selenium/Node.js/Write
# When ⏳
Tuesday, October 31, 16:00 UTC
# Where 🌍
The internet! The event will be streamed and recorded. Details coming soon.
# Why 💻
We are deprecating Ruby Selenium framework: https://phabricator.wikimedia.
See you there!
Engineering mailing list
SUMMARY: The Search Platform team (formerly part of Discovery) is planning
to fix a long-standing search bug on many wiki projects by disabling the
code in CirrusSearch that re-uses the “fallback” languages (which are
specified for user interface or system messages) for the language analysis
modules (which are used to index words in search). Deployment is planned to
start the week of October 9, 2017.
Messaging fallbacks specify what language to show a message in when there
is no message available in the language of a given wiki. A language
analysis module is language-specific software that processes text to
improve searching—so that, for example, searching for a given word will
find related forms of that word, like "hope, hopes, hoping, hoped" or
"resume, resumé, résumé" on English-language wikis.
Fallback languages for system messages make sense for historical and
cultural reasons—a reader of the Chechen Wikipedia is more likely to
understand a user interface or system message in Russian than in French,
Greek, Hindi, Italian, or Japanese—but the fallbacks don't necessarily make
any linguistic sense. Chechen and Russian, for example, are from unrelated
language families; while the languages have undoubtedly influenced one
another, their grammars are completed different.
We will deploy the software change that disables using messaging fallbacks
for language analysis fallbacks in about two weeks (targeting the week of
October 9, 2017), with any cross-language analysis exceptions explicitly
configured in a new manner. Changes will not immediately happen to all
affected wikis because each wiki in each language will need to be
re-indexed, which is a separate process that takes time. There may also be
other delays caused by Elasticsearch upgrades or other changes that need
You can also track progress of the tasks on Phabricator or read more,
see examples, and get the full list of languages affected on MediaWiki.
Sr. Software Engineer, Search Platform
This might explain the unexpectedly low results from the explore similar
test. Not saying he fix would ensure usage, but it seems we lost quite a
few events. This problem also effects autocompletd data we dashboard,
although I don't think we've used it for tests recently. Full text search
analytics should be unaffected as they don't use the mw.track functionality.
---------- Forwarded message ----------
From: "Sam Smith" <samsmith(a)wikimedia.org>
Date: Oct 12, 2017 3:41 AM
Subject: [Analytics] Heads up: mw.track client-side EventLogging mechanism
"ignored" certain events
To: "Analytics List" <analytics(a)lists.wikimedia.org>
Prior to Thursday, 28th September, if your client-side EventLogging
instrumentation logged event via mw.track, then only events tracked
during the first pageview of a user's session were logged.
Now, technically, the events weren't ignored or dropped. Instead, the
subscriber for the "event" topic was never subscribed when the module
was loaded from the ResourceLoader's cache and so events published on
that topic simply weren't received and logged.
This bug was discovered while testing some instrumentation maintained
by Readers Web  and independently by Timo Tijhof, who submitted the
ideal fix  promptly.
Timezone: BST (UTC+1)
IRC (Freenode): phuedx
Analytics mailing list