Re: [Wikitech-l] Wikimedia production excellence (September 2019)

[bawolff]

> There were five recorded incidents last month, equal to the median for
this
and last year. – Explore this data at https://codepen.io/Krinkle/full/wbYMZK

Can't help but feel something is missing here, around the 7th...

--
Brian

On Thu, Oct 24, 2019 at 11:32 PM Krinkle  wrote:

>  Read on Phabricator at
> https://phabricator.wikimedia.org/phame/post/view/173/
> ---
>
> How’d we do in our strive for operational excellence last month? Read on to
> find out!
>
> ##  Month in numbers
>
> * 5 documented incidents. [1]
> * 22 new errors reported. [2]
> * 31 error reports closed. [3]
> * 213 currently open Wikimedia-prod-error reports in total. [4]
>
> There were five recorded incidents last month, equal to the median for this
> and last year. – Explore this data at
> https://codepen.io/Krinkle/full/wbYMZK
>
> To read more about these incidents, their investigations, and pending
> actionables; check
> https://wikitech.wikimedia.org/wiki/Incident_documentation#2019
>
> ## *️⃣ A Tale of Three Great Upgrades
>
> This month saw three major upgrades across the MediaWiki stack.
>
> *Migrate from HHVM to PHP 7.2*
> The client-side switch to toggle between HHVM and PHP 7.2 saw its final
> push — from the 50% it was at previously, to 100% of page view sessions on
> 17 September. The switch further solidified on 24 September when static
> MediaWiki traffic followed suit (e.g. API and ResourceLoader). Thanks Effie
> and Giuseppe for the final push. – More details at
> https://phabricator.wikimedia.org/T219150 and
> https://phabricator.wikimedia.org/T176370.
>
> *Drop support for IE6 and IE7*
> The RFC to discontinue basic compatibility for the IE6 and IE7 browsers
> entered Last Call on 18 September. It was approved on 2 Oct (T232563).
> Thanks to Volker Eckl for leading the sprint to optimise our CSS payloads
> by removing now-redundant style rules for IE6-7 compat. – More at
> https://phabricator.wikimedia.org/T234582.
>
> *Transition from PHPUnit 4/6 to PHPUnit 8*
> With HHVM behind us, our Composer configuration no longer needs to be
> compatible with a “PHP 5.6 like” run-time. Support for the real PHP 5.6 was
> dropped over 2 years ago, and the HHVM engine supports PHP 7 features. But,
> the HHVM engine identifies as “PHP 5.6.999-hhvm”. As such, Composer refused
> to install PHPUnit 6 (which requires PHP 7.0+). Instead, Composer could
> only install PHPUnit 4 under HHVM (as for PHP 5.6). Our unit tests have had
> to remain compatible with both PHPUnit 4 and PHPUnit 6 simultaneously.
>
> Now that we’re fully on PHP 7.2+, our Composer configuration effectively
> drops PHP 5.6, 7.0 and 7.1 all at once. This means that we no longer run
> PHPUnit tests on multiple PHPUnit versions (PHPUnit 6 only). The upgrade to
> PHPUnit 8 (PHP 7.2+) is also unlocked! Thanks Max Sem, Jdforrester and
> Daimona for leading this transition. –
> https://phabricator.wikimedia.org/T192167
>
> ---
>
> ##   Outstanding reports
>
> Take a look at the workboard and look for tasks that might need your help.
> The workboard lists error reports, grouped by the month in which they were
> first observed.
>
> →  https://phabricator.wikimedia.org/tag/wikimedia-production-error/
>
> Or help someone that’s already started with their patch:
> →  https://phabricator.wikimedia.org/maniphest/query/pzVPXPeMfRIz/#R
>
> Breakdown of recent months (past two weeks not included):
>
> * February: 1 report was closed. (1 / 5 reports left).
> * March: 4 / 10 reports left (unchanged).
> * April: 8 / 14 reports left (unchanged). ⚠️
> * May: The last 4 reports were resolved. Done!
> * June: 9 of 11 reports left (unchanged). ⚠️
> * July: 4 reports were fixed! (13 / 18 reports left).
> * August: 6 reports were fixed! (8 / 4 reports left).
> * September: 12 new reports survived the month of September.
>
> ##  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/Special:PrefixIndex?prefix=Incident+documentation%2F201909=0=1=1
>
> [2] Tasks created. –
> https://phabricator.wikimedia.org/maniphest/query/XicVcsN1XkVH/#R
>
> [3] Tasks closed. –
> https://phabricator.wikimedia.org/maniphest/query/SXjsllmYHwAO/#R
>
> [4] Open tasks. –
> https://phabricator.wikimedia.org/maniphest/query/47MGY8BUDvRD/#R
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fresnel 0.5.0 for MediaWiki (perf testing in CI)

[Krinkle]

This week Fresnel 0.5.0 was released and deployed to Jenkins.

Highlighted changes:

   - Add support for Mann–Whitney U test. [1] –
   https://phabricator.wikimedia.org/T223977,
   https://en.wikipedia.org/wiki/Mann-Whitney_U_test
   - Switch regression detection from diffStdev to diffMannWhitney (for
   Paint Timing metrics).
   - Update Chromium from 73.0 to 77.0.
   - Enable Gzip for static files in web server behind Fresnel and Quibble.
   – https://gerrit.wikimedia.org/r/539427


I've written a visual guide for how to open Fresnel's performance report in
your Chrome DevTools locally:

 https://wikitech.wikimedia.org/wiki/Performance/Fresnel#DevTools

-- Timo Tijhof

Change log and tracking task for Fresnel 0.5.0:
https://github.com/wikimedia/fresnel/blob/0.5.0/CHANGELOG.md
https://phabricator.wikimedia.org/T235195

-- Forwarded message -
From: Timo Tijhof 
Subject: Fresnel for MediaWiki (performance testing)
Date: Thu, Mar 7, 2019 at 1:10 AM

You may have noticed something called "mediawiki-fresnel" leaving messages
on Gerrit patches for MediaWiki in the past few days, and wondering what
it's all about. Allow me to introduce Fresnel!

Fresnel is an automation tool for measuring and comparing client-side
performance from web pages. Fresnel was developed over the past two
quarters and is now ready for action. [1] [2] [3]

To learn more about how to use it, what it offers, and how it works, check
out:
https://wikitech.wikimedia.org/wiki/Performance/Fresnel

Some feature highlights:


   - ⏱  *Metrics* from Navigation Timing, Paint Timing, and Resource Timing
   APIs.
   -   DevTools *Timeline* from CI recording can be viewed locally in
   Chrome.
   -   Recordings take a *screenshot* available in build artefacts.
   -   Scenarios perform a *warmup* and multiple runs for more stable
   metrics.


--
Timo Tijhof

[1] Launch task: https://phabricator.wikimedia.org/T133646
[2] Phabricator project: https://phabricator.wikimedia.org/tag/fresnel/
[3] Task list:
https://phabricator.wikimedia.org/maniphest/query/9w6EAEPPLQ72/#R
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Wikimedia production excellence (September 2019)

[Krinkle]

 Read on Phabricator at
https://phabricator.wikimedia.org/phame/post/view/173/
---

How’d we do in our strive for operational excellence last month? Read on to
find out!

##  Month in numbers

* 5 documented incidents. [1]
* 22 new errors reported. [2]
* 31 error reports closed. [3]
* 213 currently open Wikimedia-prod-error reports in total. [4]

There were five recorded incidents last month, equal to the median for this
and last year. – Explore this data at https://codepen.io/Krinkle/full/wbYMZK

To read more about these incidents, their investigations, and pending
actionables; check
https://wikitech.wikimedia.org/wiki/Incident_documentation#2019

## *️⃣ A Tale of Three Great Upgrades

This month saw three major upgrades across the MediaWiki stack.

*Migrate from HHVM to PHP 7.2*
The client-side switch to toggle between HHVM and PHP 7.2 saw its final
push — from the 50% it was at previously, to 100% of page view sessions on
17 September. The switch further solidified on 24 September when static
MediaWiki traffic followed suit (e.g. API and ResourceLoader). Thanks Effie
and Giuseppe for the final push. – More details at
https://phabricator.wikimedia.org/T219150 and
https://phabricator.wikimedia.org/T176370.

*Drop support for IE6 and IE7*
The RFC to discontinue basic compatibility for the IE6 and IE7 browsers
entered Last Call on 18 September. It was approved on 2 Oct (T232563).
Thanks to Volker Eckl for leading the sprint to optimise our CSS payloads
by removing now-redundant style rules for IE6-7 compat. – More at
https://phabricator.wikimedia.org/T234582.

*Transition from PHPUnit 4/6 to PHPUnit 8*
With HHVM behind us, our Composer configuration no longer needs to be
compatible with a “PHP 5.6 like” run-time. Support for the real PHP 5.6 was
dropped over 2 years ago, and the HHVM engine supports PHP 7 features. But,
the HHVM engine identifies as “PHP 5.6.999-hhvm”. As such, Composer refused
to install PHPUnit 6 (which requires PHP 7.0+). Instead, Composer could
only install PHPUnit 4 under HHVM (as for PHP 5.6). Our unit tests have had
to remain compatible with both PHPUnit 4 and PHPUnit 6 simultaneously.

Now that we’re fully on PHP 7.2+, our Composer configuration effectively
drops PHP 5.6, 7.0 and 7.1 all at once. This means that we no longer run
PHPUnit tests on multiple PHPUnit versions (PHPUnit 6 only). The upgrade to
PHPUnit 8 (PHP 7.2+) is also unlocked! Thanks Max Sem, Jdforrester and
Daimona for leading this transition. –
https://phabricator.wikimedia.org/T192167

---

##   Outstanding reports

Take a look at the workboard and look for tasks that might need your help.
The workboard lists error reports, grouped by the month in which they were
first observed.

→  https://phabricator.wikimedia.org/tag/wikimedia-production-error/

Or help someone that’s already started with their patch:
→  https://phabricator.wikimedia.org/maniphest/query/pzVPXPeMfRIz/#R

Breakdown of recent months (past two weeks not included):

* February: 1 report was closed. (1 / 5 reports left).
* March: 4 / 10 reports left (unchanged).
* April: 8 / 14 reports left (unchanged). ⚠️
* May: The last 4 reports were resolved. Done!
* June: 9 of 11 reports left (unchanged). ⚠️
* July: 4 reports were fixed! (13 / 18 reports left).
* August: 6 reports were fixed! (8 / 4 reports left).
* September: 12 new reports survived the month of September.

##  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/Special:PrefixIndex?prefix=Incident+documentation%2F201909=0=1=1

[2] Tasks created. –
https://phabricator.wikimedia.org/maniphest/query/XicVcsN1XkVH/#R

[3] Tasks closed. –
https://phabricator.wikimedia.org/maniphest/query/SXjsllmYHwAO/#R

[4] Open tasks. –
https://phabricator.wikimedia.org/maniphest/query/47MGY8BUDvRD/#R
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikiwisdom Update and Question

[David Barratt]

Related:
https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Wikiquote/Structured_Wikiquote

On Thu, Oct 24, 2019 at 2:52 PM Adam Sobieski 
wrote:

> Wikimedia-l,
> Wikitech-l,
>
> It appears that there is a growing consensus in the discussion area for
> the Wikiwisdom sister project proposal [1] that some of the ideas which
> comprise the proposal are also feature requests for the Wikiquote project.
> These ideas include: those of a structured Wikiquote (e.g. Wikidata
> integration, individual quotes as structured data items, auto-generated
> pages from Wikidata queries (e.g. pages listing quotes by author)) as well
> as social media integration so that users could readily share individual
> quotes with one another on social media.
>
> I would like to ask how best to get the project proposal information [1]
> to the Wikiquote project team as well as how best to propose the feature
> requests to the Wikiquote project.
>
>
> Thank you,
> Adam Sobieski
>
> [1] https://meta.wikimedia.org/wiki/Wikiwisdom
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikiwisdom Update and Question

[Andre Klapper]

On Thu, 2019-10-24 at 18:51 +, Adam Sobieski wrote:
> I would like to ask how best to get the project proposal information
> [1] to the Wikiquote project team as well as how best to propose the
> feature requests to the Wikiquote project.

Not sure what a "Wikiquote project team" is, but maybe:
https://meta.wikimedia.org/wiki/Wikiquote#Project-wide_communications

Cheers,
andre
-- 
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Wikiwisdom Update and Question

[Adam Sobieski]

Wikimedia-l,
Wikitech-l,

It appears that there is a growing consensus in the discussion area for the 
Wikiwisdom sister project proposal [1] that some of the ideas which comprise 
the proposal are also feature requests for the Wikiquote project. These ideas 
include: those of a structured Wikiquote (e.g. Wikidata integration, individual 
quotes as structured data items, auto-generated pages from Wikidata queries 
(e.g. pages listing quotes by author)) as well as social media integration so 
that users could readily share individual quotes with one another on social 
media.

I would like to ask how best to get the project proposal information [1] to the 
Wikiquote project team as well as how best to propose the feature requests to 
the Wikiquote project.


Thank you,
Adam Sobieski

[1] https://meta.wikimedia.org/wiki/Wikiwisdom

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] TechCom Radar 2019-10-23

[Alexandra Paskulin]

Hi all,

Here are the minutes from this week's TechCom meeting:

* Approved: Core REST API namespace and version <
https://phabricator.wikimedia.org/T232485>.
This RFC proposes a namespace and version policy for routes in the
MediaWiki REST API.

* Last call until 2019-11-06: RFC ParallelMaintenance helper class for
multi-process maintenance
scripts .

* Hosted IRC discussion on Development policy: Require use of common
storage abstractions
.
** Minutes:
https://tools.wmflabs.org/meetbot/wikimedia-office/2019/wikimedia-office.2019-10-23-21.00.html
** Log:
https://tools.wmflabs.org/meetbot/wikimedia-office/2019/wikimedia-office.2019-10-23-21.00.log.html

* No IRC meeting next week.

You can also find our meeting minutes at


See also the TechCom RFC board
.

If you prefer you can subscribe to our newsletter here


Best,
- Alex

-- 
Alex Paskulin
Technical Writer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Ops] [Train] 1.35.0-wmf.3 status update

[Lars Wirzenius]

The blockers were quickly dealt with, thanks!

We're at 1.35.0-wmf.3 on all wikis now.

On Thu, Oct 24, 2019 at 03:30:54PM +0300, Lars Wirzenius wrote:
> The 1.35.0-wmf.3 version of MediaWiki is blocked[0].
> 
> The new version is deployed to groups 0 and 1[1], but can proceed no
> further until these issues are resolved:
> 
> * Call to undefined method
>  Wikibase\Lib\EntityTypeDefinitions::getPrefetchingTermLookupCallbacks()
>  
> 
> * Too few arguments to function
>  Wikibase\DataAccess\SingleEntitySourceServices::__construct(), 9
>  passed in /extensions/Wikibase/repo/includes/WikibaseRepo.php on line
>  2470 and exactly 10 expected
>  
> 
> Once these issues are resolved train can resume. If these issues are
> resolved on a Friday the train will resume Monday.
> 
> Thank you for your help resolving these issues!
> 
> -- Your humble train toiler
> 
> [0]. 
> [1]. 
> 
> On Tue, Oct 22, 2019 at 05:13:14PM -0600, Brennen Bearnes wrote:
> > The 1.35.0-wmf.3 version of MediaWiki is no longer blocked[0], and was
> > deployed to group 0 earlier today at 19:27 UTC, using the American
> > deploy window.
> > 
> > Thanks to andrewbogott for supplying helpful context in unblocking the
> > train, as well as hashar, thcipriani, mutante, and paladox for dealing
> > speedily with Gerrit migration issues.
> > 
> > The train should proceed to group 1 as regularly scheduled, during the
> > European deploy window.[1]
> > 
> > -- Your unassuming train minion
> > 
> > [0]. 
> > [1].
> > 
> > 
> > ___
> > Ops mailing list
> > o...@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/ops
> 
> -- 
> WMF release engineering team | he/him or they/them
> "Imagine a world in which every single human being can freely share in
> the sum of all knowledge."

-- 
WMF release engineering team | he/him or they/them
"Imagine a world in which every single human being can freely share in
the sum of all knowledge."

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Coming soon to more wikis: beta feature Reference Previews

[Johanna Strodt]

// sorry for cross-posting

Hello,

a new feature called Reference Previews [1] will soon be released as a beta
feature to more wikis. The planned deployment date is October 24 [2] around
15:00 UTC.

As you might guess from the name, this feature gives you a preview of
references in the article text. That means, you can look up a reference
without jumping down to the bottom of the page. If specified, the preview
also shows the type of a reference: whether it’s a web, journal, book or
news reference. This can help readers evaluate the trustworthiness of a
citation more quickly. If you'd like to know more about this feature,
please visit the project page.[1]

Reference Previews originated from a wish from the German-speaking wiki
community to have the preview functionality that already exists in many
wikis integrated into MediaWiki. Coordination and implementation of this
feature were done by the Technical Wishes team at Wikimedia Deutschland,
with support from the WMF’s Reading Web team. The design for the feature
was developed by the WMF. The feature is part of the MediaWiki Popups
extension [3], which is also used for the Page Previews feature.[4]

Reference Previews have been a beta feature on German and Arabic Wikipedia
for some months already, with around 3,000 users trying it out. Since then,
a few bugs were fixed, and it’s been made easier to enable the beta
feature. Now Reference Previews will become a beta feature on all
Wikipedias and on three Wikivoyage projects.[2]

We’re inviting everyone to give the feature a try: Please activate the beta
feature [5] and let us know what you think on the central feedback page
[6]! A big thanks to everyone who gave feedback so far.

If the feature isn’t available on your wiki [2] and you want to have it as
a beta feature, please reach out to us on the central feedback page.[6]

For the Technical Wishes team,

Johanna

[1] project page:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/ReferencePreviews

[2] deployment roadmap:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/ReferencePreviews#Deployment_roadmap


[3] Popups extension: https://www.mediawiki.org/wiki/Extension:Popups

[4] Page Previews: https://www.mediawiki.org/wiki/Page_Previews

[5] go to Preferences > Beta features, e.g.
https://meta.wikimedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures


[6] https://www.mediawiki.org/wiki/Help_talk:Reference_Previews

Johanna Strodt

Project Manager Community Communications Technical Wishlist, Wikimedia
Deutschland
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Ops] [Train] 1.35.0-wmf.3 status update

[Lars Wirzenius]

The 1.35.0-wmf.3 version of MediaWiki is blocked[0].

The new version is deployed to groups 0 and 1[1], but can proceed no
further until these issues are resolved:

* Call to undefined method
 Wikibase\Lib\EntityTypeDefinitions::getPrefetchingTermLookupCallbacks()
 

* Too few arguments to function
 Wikibase\DataAccess\SingleEntitySourceServices::__construct(), 9
 passed in /extensions/Wikibase/repo/includes/WikibaseRepo.php on line
 2470 and exactly 10 expected
 

Once these issues are resolved train can resume. If these issues are
resolved on a Friday the train will resume Monday.

Thank you for your help resolving these issues!

-- Your humble train toiler

[0]. 
[1]. 

On Tue, Oct 22, 2019 at 05:13:14PM -0600, Brennen Bearnes wrote:
> The 1.35.0-wmf.3 version of MediaWiki is no longer blocked[0], and was
> deployed to group 0 earlier today at 19:27 UTC, using the American
> deploy window.
> 
> Thanks to andrewbogott for supplying helpful context in unblocking the
> train, as well as hashar, thcipriani, mutante, and paladox for dealing
> speedily with Gerrit migration issues.
> 
> The train should proceed to group 1 as regularly scheduled, during the
> European deploy window.[1]
> 
> -- Your unassuming train minion
> 
> [0]. 
> [1].
> 
> 
> ___
> Ops mailing list
> o...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/ops

-- 
WMF release engineering team | he/him or they/them
"Imagine a world in which every single human being can freely share in
the sum of all knowledge."

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l