All wikis were rolled back to 1.28.0-wmf.8 last night due to an increase
in https://phabricator.wikimedia.org/T119736 . We're working on it, and
will either go back to 1.28.0-wmf.9, or to 1.28.0-wmf.10 (at normal
train pace) when it's resolved.
Matt
I've split the Flow MediaWiki-Vagrant role into two, to make things
simpler for casual Flow users.
If you don't have the Flow role enabled, you can stop reading now.
The basic 'flow' role will no longer depend on External Store and other
optional dependencies.
You now need to do one of these things:
---
TLDR: If you use Flow on Vagrant regularly, enable wikimediaflow.
Otherwise, enable externalstore or destroy your Vagrant.
---
* Enable 'wikimediaflow' (if you care about existing Flow content).
This will bring in the optional dependencies again, and leave your
content as-is.
* Enable 'externalstore' (if you care about existing non-Flow content
that is using External Store already). Avoids the other optional
dependencies, but brings in External Store, so existing External Store
content can be read.
* Manually tweak configuration
* Just ignore the problems with old content
* Destroy and re-create your Vagrant (this will destroy the invalid
content that points to no-longer-existing External Store, and leave you
with a simpler config).
Matt
Hi everyone,
I am trying to configure a mysql server for our wikimedia service. We are using ipv6 of the mysql server.
I am not sure how to configure $wgDBServer with an ipv6. I am able to configure the server with ipv6.
I tried to set:
1. $wgDBServer = [IPAddress]:Portname
2. $wgDBServer = IPAddress
But none of the above works for me.
Thanks very much in advance.
-------- Forwarded Message --------
Subject: [action required] We are removing inactive projects.
Date: Fri, 8 Jul 2016 11:09:38 -0500
From: Andrew Bogott <andrewbogott(a)gmail.com>
Reply-To: andrewbogott(a)gmail.com
To: labs-announce(a)lists.wikimedia.org
If you are exclusively a user of tool labs, you can ignore this email.
If you use or administer another labs project, this email REQUIRES
ACTION ON YOUR PART.
We are reclaiming unused resources due to an ongoing shortage.
Visit this page and add a signature under projects you know to be active:
https://wikitech.wikimedia.org/wiki/Purge_2016
Associated wmflabs.org <http://wmflabs.org> domains are included to
identify projects by offered services.
We are not investigating why projects are needed at this time. If one
person votes to preserve then we will do so in this round of cleanup.
In a month, projects and associated instances not claimed will be
suspended or shutdown. A month later if no one complains these projects
will be deleted..
- Andrew (on behalf of all Labs Admins everywhere)
Hello,
The Wikimedia Foundation Discovery Search team
<https://www.mediawiki.org/wiki/Wikimedia_Discovery/Search> has recently
discovered
<https://commons.wikimedia.org/wiki/File:From_Zero_to_Hero_-_Anticipating_Ze…>
that search queries that end with a question mark (i.e. "*how old is Tom
Cruise?*") can sometimes lead to zero (or unusable) results being returned.
This zero result rate is one of the primary ways that the Search team
determines how much our users are satisfied with their query results
<http://discovery.wmflabs.org/metrics/#kpi_zero_results>.
In order to improve the results that queries containing a questions mark,
we'd like to change the behavior of the search on the backend. However, we
would love to have feedback from the community to make sure that this is a
smart change to do.
If you are interested in how search works, or see this change as a possible
disruption for your work, please learn more about this potential change
<https://meta.wikimedia.org/wiki/Discovery/Handling_question_marks_in_search…>
and let us know your thoughts.
Cheers from the Discovery Search team!
--
Deb Tankersley
Product Manager, Discovery
IRC: debt
Wikimedia Foundation
Hi folks,
Right now our CI infrastructure (Zuul/Jenkins/Nodepool) are having a bad
day and aren't able
to spawn new instances to perform tests. The outage is ongoing and there
isn't an ETA for
restoration of service just yet.
In the meantime: please avoid force-merging (doing the Verified+2 check
yourself) and skipping
Jenkins unless you're dealing with an urgent production issue that must
land today. Doing so
makes Zuul get extra noisy which makes further diagnosis difficult.
Thanks for your patience!
-Chad & rest of RelEng