Hello,
The 1.39.0-wmf.39 is blocked, immediately after deploying it to group0
wikis, Flow topics ended up being error pages.
When browsing a topic page, there are two issues bubbling up in logstash:
>From VectorTemplate->buildSidebar()
* /srv/mediawiki/php-1.35.0-wmf.39/includes/language/Message.php:261
$key must be a string or an array
>From Skin->buildSidebar / ElectronPdfServiceHooks::onSidebarBeforeOutput
*
/srv/mediawiki/php-1.35.0-wmf.39/extensions/ElectronPdfService/src/ElectronPdfServiceHooks.php:62
PHP Notice: Undefined index: print
Which as I understand it causes an exception.
The breaking bug is: https://phabricator.wikimedia.org/T256761
--
Antoine "hashar" Musso
Release Engineering
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds
office hours the first Wednesday of each month. Come talk to us about
anything related to Wikimedia search!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, July 1st, 2020
Time: 15:00-16:00 GMT / 08:00-09:00 PDT / 11:00-12:00 EDT / 17:00-18:00 CEST
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vyc-jvgq-dww
Join by phone in the US: +1 786-701-6904 PIN: 262 122 849#
Hope to talk to you in a week!
—Trey
Trey Jones
Sr. Software Engineer, Search Platform
Wikimedia Foundation
UTC-4 / EDT
Hello everyone,
In the interest of proceeding with the deprecation of Jessie in our
infrastructure, SRE ServiceOps will stop maintaining and eventually
remove the base Debian Jessie OCI container image[1], also known as
wikimedia-jessie, from our docker registry.
If you rely on this image in any way, you are strongly urged to move
to our Debian Stretch or Buster images, which will continue to be
maintained for some time (for more information see
https://wikitech.wikimedia.org/wiki/Operating_system_upgrade_policy).
A tentative timeline follows:
* 2020-07-02. https://gerrit.wikimedia.org/r/c/operations/puppet/+/587529
will be merged. This will mean the image will no longer be receiving
any kind of updates but will still be possible to be pulled from the
registry. Workflows are not expected to break.
* 2020-08-03. Removal of all the image tags and versions of the above
image will happen. That will mean that the image will no longer be
able to be pulled from the registry. If you have any workflows that
rely on pulling this image from the registry, they are expected to
break on this date. Images that have already been published and are
based on the Jessie image however will not be touched and will still
be pullable.
If you have a workflow that will break after the 2020-08-03 mark and
are unable to alter it, please reach out to us.
Following the above, we will also investigate whether removing image
versions and tags that depend on the removed image makes sense.
Note that this is the first time we remove a base image from our
registry and as such we are building knowledge and experience around
this.
[1] https://tools.wmflabs.org/dockerregistry/wikimedia-jessie/tags/
Regards,
--
Alexandros Kosiaris
Principal Site Reliability Engineer
Wikimedia Foundation
Hello everyone!
We are super excited to introduce two new bots for Wikimedia’s Zulip<https://wikimedia.zulipchat.com> - goodbot and ircbot!
Wikimedia has been using Zulip<https://zulipchat.com/>, an open source communication platform, for supporting participants in Wikimedia’s outreach programs. Read more about how we are building a community in this blog post: https://techblog.wikimedia.org/2020/05/04/using-zulip-an-open-source-tool-f…. As a part of Google Summer of Code<https://summerofcode.withgoogle.com/> 2020, QEDK<https://www.mediawiki.org/wiki/User:QEDK> is working towards developing bots to make the Zulip experience better for participants, mentors and administrators.
Goodbot is a chatbot that sends welcome messages to newly joined participants and helps answer some questions about the different outreach programs like Google Summer of Code, Outreachy and Season of Docs. You can chat with it on any Wikimedia Zulip stream.
Ircbot bridges all communication between the #technical-support<https://wikimedia.zulipchat.com/#streams/technical-support> stream on Zulip and the IRC channel #wikimedia-tech. It allows the participant community on Zulip to interact with the broader Wikimedia community that is primarily active on IRC. You can see ircbot active in both the aforementioned channels.
You can learn more about the future plans for the project in the GSoC proposal here: https://phabricator.wikimedia.org/T247879 and keep track of the progress in the bi-weekly reports recorded here: https://www.mediawiki.org/wiki/User:QEDK
We would love to hear your thoughts and feedback on the bots. Please reach out to us on Zulip: https://wikimedia.zulipchat.com/ or on GitHub: https://github.com/qedk/goodbot. :)
Thanks and cheers,
The goodbot team
Based on recent CRs and feedback I've redesigned the recently updated
Stable interface policy.
Old:
https://www.mediawiki.org/w/index.php?title=Stable_interface_policy&oldid=3…
New:
https://www.mediawiki.org/wiki/User:Krinkle/Stable_interface_policy
I hope this is more approachable and easier to navigate from the various
perspectives and use cases where you might need it (e.g. when reviewing
code, writing code in core, writing code in an extension, planning out the
deprecation roadmap for a feature, etc.).
This page is currently a draft because during the rewrite I noticed a few
minor inconsistencies and open questions in the nominal text. These are
being fleshed out through an RFC at <
https://phabricator.wikimedia.org/T255803>. Once we've decided on those
details, I'll publish the new design to the canonical page.
-- Timo
Everyone on Wikimedia wikis will shortly be logged out and will have
to log back in again.
We are resetting all sessions because we believe that, due to a
configuration error, session cookies may have been sent in cacheable
responses. Some users reported that they saw the site as if they were
logged in as someone else. We believe that the number of affected
users was very small. However, we believe that resetting all sessions
is a prudent measure to ensure that the impact is limited.
There are several layers of protection against something like this
happening, and we don't yet know how all of them failed, but we have
made a configuration change which should be sufficient to prevent it
from happening again.
-- Tim Starling
Greetings-
With the security/maintenance release of MediaWiki 1.31.8/1.33.4/1.34.2
[0], we would also like to provide this supplementary announcement of
MediaWiki extensions and skins with now-public Phabricator tasks, security
patches and backports [1]:
== CentralAuth ==
+ (T250594, CVE-2020-12051) - globaluserinfo api allows access to
information about hidden users
<
https://gerrit.wikimedia.org/r/#/q/I3c80641dc1202df7428714f0ca44717a51ff6021
>
The Wikimedia Security Team recommends updating these extensions and/or
skins to the current master branch or relevant, supported release branch
[2] as soon as possible. Some of the referenced Phabricator tasks above
_may_ still be private. Unfortunately, when security issues are reported,
sometimes sensitive information is exposed and since Phabricator is
historical, we cannot make these tasks public without exposing this
sensitive information. If you have any additional questions or concerns
regarding this update, please feel free to contact security(a)wikimedia.org
or file a security task within Phabricator [3].
[0]
https://lists.wikimedia.org/pipermail/mediawiki-announce/2020-June/000252.h…
[1] https://phabricator.wikimedia.org/T248542
[2] https://www.mediawiki.org/wiki/Version_lifecycle
[3] https://www.mediawiki.org/wiki/Reporting_security_bugs
--
Scott Bassett
sbassett(a)wikimedia.org
📘 Read on Phabricator at
https://phabricator.wikimedia.org/phame/post/view/198/
-------
How’d we do in our strive for operational excellence last month? Read on to
find out!
## 📊 Month in numbers
* 5 documented incidents in May. [1]
* 28 new production error tasks filed in May. [2] [3]
* 68 recent production errors currently open (up from 61).
* 193 currently open Wikimedia-prod-error tasks (up from 178). [4]
For more about recent incidents and pending actionables see Wikitech and
Phabricator, at https://wikitech.wikimedia.org/wiki/Incident_documentation
and https://phabricator.wikimedia.org/project/view/4758
## 📉 Outstanding reports
Take a look at the workboard and look for tasks that could use your help.
→ https://phabricator.wikimedia.org/tag/wikimedia-production-error/
Breakdown of recent months:
* July 2019: One task closed, 7 of 18 tasks left. ⚠️
* August: 2 of 14 tasks left (unchanged).
* September: 7 of 12 tasks left (unchanged).
* October: 4 of 12 tasks left (unchanged).
* November: 4 of 5 tasks left (unchanged).
* December: 4 of 9 tasks left (unchanged).
* January 2020: 5 of 7 tasks left (unchanged).
* February: Two tasks closed, 4 of 7 tasks left. ⚠️
* March: 2 of 2 tasks left (unchanged).
* April: 14 of 14 tasks left (unchanged).
* May: 14 new tasks survived the month of May.
At the end of April the total of open production errors over recent months
was 61. Of those, 7 got closed, but with 14 new tasks from May still open,
the total has grown to 68.
The workboard had 178 open tasks in April, which saw a steep increase to
now 192 open tasks (this includes June 2020 so far, and pre-2019 tasks).
## 🎉 Thanks!
Thank you to everyone else who helped by reporting, investigating, or
resolving problems in Wikimedia production. Thanks!
Until next time,
– Timo Tijhof
-------
Footnotes:
[1] Incidents. –
https://wikitech.wikimedia.org/wiki/Incident_documentation#2020
[2] Tasks created. –
https://phabricator.wikimedia.org/maniphest/query/7Z4Us2BS02Uo/#R
[3] Tasks closed. –
https://phabricator.wikimedia.org/maniphest/query/FoIFMu5UO8pw/#R
[4] Open tasks. –
https://phabricator.wikimedia.org/maniphest/query/Fw3RdXt1Sdxp/#R