Wikitech-l February 2019

wikitech-l@lists.wikimedia.org

56 participants
63 discussions

2019-02-13 Scrum of Scrums meeting notes
by Grace Gellerman 13 Feb '19

13 Feb '19

https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-02-13 = 2019-02-13 = == Callouts == * Fundraising campaigns https://meta.wikimedia.org/wiki/CentralNotice/Calendar * Release Engineering: Beta Cluster and CI issues https://lists.wikimedia.org/pipermail/cloud/2019-February/000538.html * SRE: Sunsetting Wikipedia Zero stuff ( https://phabricator.wikimedia.org/T187716) is blocked by https://phabricator.wikimedia.org/T213769 (and possibly others); not urgent, but we want this done this quarter if possible. * From Analytics: The old staging database in dbstore1002 will be set to read-only on Feb 18th. Please, use the new one in dbstore1005, thanks! * TechCom: RFC: Re-establish the development policies https://phabricator.wikimedia.org/T190379 == Audiences == === Contributors === ==== Community Tech ==== * Blocked by: * Blocking: * Updates: ** ==== Anti-Harassment Tools ==== * Blocked by: * Blocking: * Updates: ** ==== Editing ==== * Blocked by: * Blocking: ** Updates: ** ==== Growth ==== * Blocked by: * Blocking: * Updates: ** ==== Language ==== * Blocked by: * Blocking: * Updates: ** === Readers === ==== iOS native app ==== * Blocked by: * Blocking: * Updates: **In a code freeze phase for 6.2 - testing https://phabricator.wikimedia.org/tag/ios-app-v6.2-beluga-on-a-pogo-stick/ **Preapring for 6.2.1 - bug fixes, editing tools enhancements and mobile html prototype https://phabricator.wikimedia.org/tag/ios-app-v6.2.1-beluga-on-stilts/ ==== Android native app ==== * Blocked by: * Blocking: * Updates: ** ==== Readers Web ==== * Blocked by: * Blocking: * Updates: ** Summary: we've transitioned the Proton PDF renderer to Readers Infrastructure for final deployment, we're continuing the Advanced Mobile Contributions project and have enabled ES6 support in MobileFrontend as part of the Architecture investment effort. ** Responsive website (MinervaNeue / MobileFrontend): *** Advanced mobile contributions https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions **** Talk tabs disabled on main page T214724 **** Page/talk toggle v1 T212216 **** Design updates to Settings page & opt-in toggle T214195 **** Create AMC edit tag T212959 *** Invest in the MobileFrontend & MinervaNeue frontend architecture https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFro… **** Enable Babel transpiling in MobileFrontend T202746 **** Separate lazy loading from Skin T214658 **** Migrate deprecated calls T208915 **** Group web client error reports T212970 *** Page issues https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues **** Miscellaneous bug fixes and maintenance T212376 T212371 T214550 *** ExternalGuidance extension review and support *** Miscellaneous bug fixes and maintenance T215648 T215849 T213336 T202374 ** Desktop website (Vector, Popups) *** Popups https://www.mediawiki.org/wiki/Page_Previews **** WMDE reference previews review and support T67114 https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/ReferencePreviews ** PDF rendering (Proton) https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality *** Transitioned to Readers Infrastructure ==== Readers Infrastructure ==== * Blocked by: ** SRE: Sunsetting Wikipedia Zero stuff ( https://phabricator.wikimedia.org/T187716) is blocked by https://phabricator.wikimedia.org/T213769 (and possibly others); not urgent, but we want this done this quarter if possible. * Blocking: * Updates: ** Maps: codfw cluster OS upgrade to stretch started this week with maps2004 T215521 ** App Editor Tasks infrastructure work ongoing ==== Multimedia ==== * Blocked by: ** RelEng: Adding WikibaseMediaInfo to the gate; patch is https://gerrit.wikimedia.org/r/c/integration/config/+/480463 and needs deployment * Blocking: ** * Updates ** working towards first release of structured data statements (depicts) ** onboarding for 2 new hires ==== Parsing ==== * Blocked by: * Blocking: * Updates: ==== UI Standardization ==== * Blocked by: * Blocking: * Updates: ** == Technology == === Analytics === * Blocked by: * Blocking: * Updates: ** The replacement for dbstore1002 is in place now. Contains a queryable replica of the wiki databases distributed in 3 nodes (dbstore100[345]). ** Up-to-date docs at: https://wikitech.wikimedia.org/wiki/Analytics/Data_access#MariaDB_replicas ** The staging database is in dbstore1005. The old one in dbstore1002 will be set to read-only on Feb 18th. And we plan to decomission dbstore1002 in the upcoming weeks. ** Superset can connect to the new MySQL hosts, including the staging database. === Cloud Services === * Blocked by: * Blocking: * Updates: ** === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** Still testing PHP7 / MediaWiki 1.31 payments-wiki upgrade, has morphed into testing our backup cluster as well https://phabricator.wikimedia.org/T184460 ** Fixing bugs in latest CiviCRM point upgrade https://phabricator.wikimedia.org/T215802, https://phabricator.wikimedia.org/T215513 ** Updating employer matching gift import https://phabricator.wikimedia.org/T215196 ** Donor data deletion tool updates https://phabricator.wikimedia.org/T199747 ** Determining viability of ways to ask for a recurring donation after getting a one-time donation https://phabricator.wikimedia.org/T215340 ** Reducing number of emails sent to recurring donors https://phabricator.wikimedia.org/T213209 ** Creating batch fraud lookup tool https://phabricator.wikimedia.org/T199268 === MediaWiki Core Platform === * Blocked by: * Blocking: * Updates: ** Marko taking over coordination of Multi-DC work ** Overview doc for Q3 code cleanup work: Q3 cleanup work: https://www.mediawiki.org/wiki/User:BPirkle_(WMF)/Code_Cleanup_FY2019_Q3 ** Publishing of Platform Evolution Goals and an Update *** https://www.mediawiki.org/wiki/Platform_Evolution/Goals *** https://www.mediawiki.org/wiki/Platform_Evolution/Updates/Feb_2019 ** Session Service work continues (added http metrics, syslog messages, CI tests and began documentation) https://phabricator.wikimedia.org/T206016 ** ObjectCache/Stash analysis: https://www.mediawiki.org/wiki/User:EvanProdromou/ObjectCache_use === Performance === * Blocked by: ** * Blocking: ** * Updates: ** Switched from c4.large to c5.xlarge for the WebPageTest agent https://phabricator.wikimedia.org/T215167 - This means metrics id decreased since the machine is faster ** RFC: Re-establish the development policies https://phabricator.wikimedia.org/T190379 (hoping to be on Last Call soon) ** Reviewed ExternalGuidance Extension for Language Team https://phabricator.wikimedia.org/T214170 === Release Engineering === * Blocked by: ** * Blocking: ** Multimedia: Adding WikibaseMediaInfo to the gate; patch is https://gerrit.wikimedia.org/r/c/integration/config/+/480463 and needs deployment ** Scoring Platform: sort of because we have a work-around. https://phabricator.wikimedia.org/T212818 (LFS not mirroring to gerrit) * Updates: ** Beta Cluster and CI issues https://lists.wikimedia.org/pipermail/cloud/2019-February/000538.html ** Train Health: *** Last week: 1.33.0-wmf.16 - https://phabricator.wikimedia.org/T206670 *** This week: 1.33.0-wmf.17 - https://phabricator.wikimedia.org/T206671 *** Next week: 1.33.0-wmf.18 - https://phabricator.wikimedia.org/T206672 ** Log Health: ** Code Health: === Research === * Blocked by: None * Blocking: None * Updates: ** Links event stream is going live soon (end of week or next week): *** https://phabricator.wikimedia.org/T214706 ** Continuing work on productionizing article recommender systems: *** https://phabricator.wikimedia.org/T211981 ** Experimental section alignment and recommendation API: *** https://meta.wikimedia.org/wiki/Research:Expanding_Wikipedia_articles_acros… *** https://secrec.wmflabs.org/API/alignment/es/en/Historia *** https://secrec.wmflabs.org/API/recommendation/en/Quilombo?verbose=False&bli… === Scoring Platform === * Blocked by: * Releng -- sort of because we have a work-around. https://phabricator.wikimedia.org/T212818(LFS not mirroring to gerrit) * Blocking: * Growth -- Fixing an issue with itwiki's goodfaith model (thank you Roan!) https://phabricator.wikimedia.org/T211032 * Updates: * Damagaing/goodfaith support for Korean Wikipedia coming soon https://phabricator.wikimedia.org/T161629 * New ORES deployment on the way out - * Increased fitness for English Wikipedia Draft Quality and Article Quality (T214091) - * Increased fitness for Wikidata Item Quality model (T158430) - * Reduced potential security issues (pyyaml T214159 & pickle-->json T206333) - * New models for Spanish Wikiquote (T209784) === Search Platform === * Blocked by: * Blocking: * Updates: ** Finished A/B tests for wbsearchentities profiles for FR, DE and ES: https://phabricator.wikimedia.org/T214515 - results positive ** Removed “archive” type indexes in preparation for Elastic 6 migration: https://phabricator.wikimedia.org/T213851 ** Re-built Hebmorph analysis plugin: https://phabricator.wikimedia.org/T214439 ** Finished setting up work environment for NLP contractor: https://phabricator.wikimedia.org/T212885 ** Fixed WDQS issues where some triples had duplicated normalized value: https://phabricator.wikimedia.org/T213213 ** Working on ES 6 upgrade: https://phabricator.wikimedia.org/T183282 ** Working on running multiple Elastic instances on the same hardware: https://phabricator.wikimedia.org/T193654 ** Working on “wrong keyboard” detection: https://phabricator.wikimedia.org/T138958 ** Working on query parsing refactoring: https://phabricator.wikimedia.org/T185108 ** Working on moving CirrusSearch code out of Wikibase to a separate extension: https://phabricator.wikimedia.org/T190022 === Security === * Blocked by:None * Blocking:None * Updates:T215048: waiting on code to review **T155537 and T156960: to be submitted for consideration for outsourcing **T207246: either to review in next two weeks or moved to frozen **T214152: review to be finished today **T201492: to be completed end of next week **T163827: to be completed end of week **T163827: tbd **T207990: tbd === Services === * Blocked by: * Blocking: * Updates: ** === Site Reliability Engineering === * Blocked by: ** None * Blocking: ** None * Updates: ** Goal work ongoing ** eventgate being deployed this week == Wikidata == * Blocked by: * Blocking: * Updates: ** == German Technical Wishlist == * Blocked by: * Blocking: * Updates: ** == Multi-Content Revisions == * Blocked by: * Blocking: * Updates: ** == SoS Meeting Bookkeeping == * Updates: **

1 0

Beta Cluster and CI issues (was Fwd: [Cloud] [Cloud-announce] VPS hardware failure -- downtime ongoing)
by Greg Grossmeier 13 Feb '19

13 Feb '19

This WMCS outage is affecting Beta Cluster (aka: deployment-pre VPS project) and our CI build/test servers (aka: the integration project). Apologies for any downtime and/or slow CI responses while this is being sorted. Greg ----- Forwarded message from Andrew Bogott <abogott(a)wikimedia.org> ----- > Date: Wed, 13 Feb 2019 07:25:39 -0600 > From: Andrew Bogott <abogott(a)wikimedia.org> > To: Cloud-announce(a)lists.wikimedia.org > Subject: [Cloud] [Cloud-announce] VPS hardware failure -- downtime ongoing > Reply-To: cloud(a)lists.wikimedia.org > > We're currently experiencing a mysterious hareware failure in our datacenter > -- three different SSDs failed overnight, two of them in cloudvirt1018 and > one of them in cloudvirt1024. The VMs on 1018 are down entirely. We may > move those on 1024 to another host shortly in order to guard against > additional drive failure. > > There's some possibility that we will experience permanent data loss on > cloudvirt1018, but everyone is working hard to avoid this. > > The following VMs are on cloudvirt1018: > > > a11y | reading-web-staging > abogott-scapserver | testlabs > af-puppetdb01 | automation-framework > api | openocr > asdf | quotatest > bastion-eqiad1-02 | bastion > clm-test-01 | community-labs-monitoring > compiler1002 | puppet-diffs > cyberbot-exec-iabot-01 | cyberbot > deployment-db03 | deployment-prep > deployment-db04 | deployment-prep > deployment-memc05 | deployment-prep > deployment-pdfrender02 | deployment-prep > deployment-sca01 | deployment-prep > design-lsg3 | design > eventmetrics-dev01 | eventmetrics > fridolin | catgraph > gtirloni-puppetmaster-01 | testlabs > hadoop-master-3 | analytics > ign | ign2commons > integration-castor03 | integration > integration-slave-docker-1017 | integration > integration-slave-docker-1033 | integration > integration-slave-docker-1038 | integration > integration-slave-jessie-1003 | integration > integration-slave-jessie-android | integration > k8s-master-01 | general-k8s > k8s-node-03 | general-k8s > k8s-node-05 | general-k8s > k8s-node-06 | general-k8s > kdc | analytics > labstash-jessie1 | logging > language-mleb-legacy | language > login-test | catgraph > lsg-01 | design > mathosphere | math > mc-clusterA-1 | test-twemproxy > mwoffliner5 | mwoffliner > novaadminmadethis-4 | quotatest > ntp-01 | cloudinfra > ntp-02 | cloudinfra > ogvjs-testing | ogvjs-integration > phragile-pro | phragile > planet-hotdog | planet > pub2 | wikiapiary > puppenmeister | planet > puppet-compiler-v4-other | testlabs > puppet-compiler-v4-tools | testlabs > quarry-beta-01 | quarry > signwriting-swis | signwriting > signwriting-swserver | signwriting > social-tools3 | social-tools > striker-deploy04 | striker > striker-puppet01 | striker > t166878 | otrs > togetherjs | visualeditor > tools-sgebastion-06 | tools > tools-sgeexec-0902 | tools > tools-sgeexec-0903 | tools > tools-sgewebgrid-generic-0901 | tools > tools-sgewebgrid-lighttpd-0901 | tools > ve-font | design > wikibase1 | sciencesource > wikicitevis-prod | wikicitevis > wikifarm | pluggableauth > women-in-red | globaleducation > > > > _______________________________________________ > Wikimedia Cloud Services announce mailing list > Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org) > https://lists.wikimedia.org/mailman/listinfo/cloud-announce > _______________________________________________ > Wikimedia Cloud Services mailing list > Cloud(a)lists.wikimedia.org (formerly labs-l(a)lists.wikimedia.org) > https://lists.wikimedia.org/mailman/listinfo/cloud ----- End forwarded message ----- -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | Release Team Manager A18D 1138 8E47 FAC8 1C7D |

1 0

MediaWiki PHP coding conventions for declaring return types
by Brad Jorsch (Anomie) 13 Feb '19

13 Feb '19

I've started a discussion at https://www.mediawiki.org/wiki/Manual_talk:Coding_conventions/PHP#Declaring…. Please comment there if interested. -- Brad Jorsch (Anomie) Senior Software Engineer Wikimedia Foundation

1 0

Wikimedia production excellence (January 2019)
by Krinkle 13 Feb '19

13 Feb '19

📘 (est. 3 minute read) https://phabricator.wikimedia.org/phame/live/1/post/140/ ------- How’d we do in our strive for operational excellence last month? Read on to find out! - Month in numbers. - Highlighted stories. - Current problems. ## 📊 *Month in numbers* * 4 documented incidents in January 2019. [1] * 16 Wikimedia-prod-error tasks closed. [2] * 17 Wikimedia-prod-error tasks created. [3] ## *️⃣ *Unable to move certain file pages* Xiplus reported that renaming a File page on zh.wikipedia.org led to a fatal database exception. Andre Klapper identified the stack trace from the logs, and Brad (Anomie) investigated. The File renaming failed because the File page did not have a media file associated with it (such move action is not currently allowed in MediaWiki). But, while handling this error the code caused a different error. The impact was that the user didn't get informed about why the move failed. Instead, they received a generic error page about a fatal database exception. Brad fixed the code a few hours later, and it was deployed by Roan later that same day. Thanks! — https://phabricator.wikimedia.org/T213168 ## *️⃣ *DBPerformance regression detected and fixed* During a routine audit of Logstash dashboards, I found a DBPerformance warning. The warning indicated that the limit of 0 for “master connections” was violated. That's a cryptic way of saying it found code in MediaWiki that uses a database master connection on a regular page view. MediaWiki can have many replica database servers, but there can be only one master database at any given moment. To reduce chances of overload, delaying edits, or network congestion; we make sure to use replicas whenever possible. We usually involve the master only when source data is being changed, or is about to be changed. For example, when editing a page, or saving changes. As the vast majority of traffic is page views, we have lower thresholds for latency and dependency on page views. In particular, page views may (in the future) be routed to secondary data centres that don’t even have a master DB. Tchanders from the Anti-Harassment tea) investigated the issue, found the culprit, and fixed it in time for the next MediaWiki train. Thanks! — https://phabricator.wikimedia.org/T214735 ## *️⃣ *TemplateData missing in action* Tacsipacsi and Evad37 both independently reported the same TemplateData issue. TemplateData powers the template insertion dialog in VisualEditor. It wasn't working for some templates after we deployed the 1.33-wmf.13 branch. The error was “Argument 1 passed to ApiResult::setIndexedTagName() must be an instance of array, null given”. This means there was code that calls a function with the wrong parameter. For example, the variable name may've been misspelled, or it may've been the wrong variable, or (in this case) the variable didn't exist. In such case, PHP implicitly assumes “null”. Bartosz (Matmarex) found the culprit. The week before, I made a change to TemplateData that changed the “template parameter order” feature to be optional. This allows users to decide whether VisualEditor should force an order for the parameters in the wikitext. It turned out I forgot to update one of the references to this variable, which still assumed it was always present. Brad (Anomie) fixed it later that week, and it was deployed the next day. Thanks! — https://phabricator.wikimedia.org/T213953 ## 📈 *Current problems* Take a look at the workboard and look for tasks that might need your help. The workboard lists known issues, grouped by the week in which they were first observed. → https://phabricator.wikimedia.org/tag/wikimedia-production-error/ There are currently 188 open Wikimedia-prod-error tasks as of 12 February 2019. (We’ve had a slight increase since November; 165 in December, 172 in January.) For this month’s edition, I’d like to draw attention to a few older issues that are still reproducible: * [2013; Collection extension] Special:Book fatal error for blocked users. — https://phabricator.wikimedia.org/T56179 * [2013; CentralNotice] Fatal error when placeholder key contains a space. — https://phabricator.wikimedia.org/T58105 * [2014; LQT] Fatal error when attempting to view certain threads. — https://phabricator.wikimedia.org/T61791 * [2015; MassMessage] Warning about Invalid message parameters. — https://phabricator.wikimedia.org/T93110 * [2015; Wikibase] Warning “UnresolvedRedirectException” for some pages on Wikidata (and Commons). — https://phabricator.wikimedia.org/T93273 ## 💡Terminology A “Fatal error” (or uncaught exception) prevents a user action. For example — a page might display “MWException: Unknown class NotificationCount.”, instead the article content. A “Warning” (or non-fatal, or PHP error) lets the program continue to display a mostly page regardless. This may cause corrupt, incorrect, or incomplete information to be shown. For example — a user may receive a notification that says “You have (null) new messages”. ## 🎉 Thanks! Thank you to everyone who has helped by reporting, investigating, or resolving problems in Wikimedia production. Including: Xiplus‚ Anomie, Daimona Gilles, He7d3r, Jdforrester, MatmaRex, MModell, Nikerabbit, Catrope, Tchanders, Tgr, and Thiemo. Thanks! Until next time, – Timo Tijhof 👢*There's a snake in my boot. Reach for the sky!* ------- Footnotes: [1] Incidents. – https://wikitech.wikimedia.org/wiki/Special:AllPages?from=Incident+document… [2] Tasks closed. – https://phabricator.wikimedia.org/maniphest/query/COTGbmxGcm_l/#R [3] Tasks created. – https://phabricator.wikimedia.org/maniphest/query/DLRuzOg9bSJA/#R

2 1

Thank you Tuesday
by Krinkle 12 Feb '19

12 Feb '19

Hi, Noticed something neat or cool that someone did? Or is someone just being awesome in general? Take this opportunity to say thanks! * Thanks to Christian (QChris) for the many years of helping administrate Gerrit repositories, both during his work as WMF staff, and in the 4 years since then. * Thanks to Kunal (Legoktm) for re-starting our Thank you threads as a weekly occurrence. Who would you like to thank? -- Timo Tijhof (Krinkle)

2 1

Platform Evolution Update
by Corey Floyd 12 Feb '19

12 Feb '19

Hi all, The PE Program team has been preparing for the Wikimedia Foundation midterm (3 year) planning by reviewing and organizing all of the followup from TechConf. We published an update of this work on Wiki here: https://www.mediawiki.org/wiki/Platform_Evolution/Updates/Feb_2019 A list of oiuyr proposed Goals and Outcomes for the next 3 years is here: https://www.mediawiki.org/wiki/Platform_Evolution/Goals We are currently looking for feedback on the work we have done so far, please check out the update for more info. Thanks everyone! -- Corey Floyd Director of Engineering, Core Platform Wikimedia Foundation cfloyd(a)wikimedia.org

1 0

Wednesday: Technical Advice IRC Meeting
by Michael Schönitzer 11 Feb '19

11 Feb '19

Reminder: Technical Advice IRC meeting this week **(Wednesday) 4-5 pm UTC** on #wikimedia-tech. Question can be asked in English & Persian. The Technical Advice IRC Meeting is a weekly support event for volunteer developers. Every Wednesday, two full-time developers are available to help you with all your questions about Mediawiki, gadgets, tools and more! This can be anything from "how to get started" over "who would be the best contact for X" to specific questions on your project. If you know already what you would like to discuss or ask, please add your topic to the next meeting: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting Hope to see you there! Michi (for the Technical Advice IRC Meeting crew) -- Michael F. Schönitzer Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Tel. (030) 219 158 26-0 https://wikimedia.de Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit teilhaben, es nutzen und mehren können. Helfen Sie uns dabei! https://spenden.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

GSOC' 19 idea proposal [waiting to be accepted :) ]
by K. Kaushik Reddy 11 Feb '19

11 Feb '19

Hi people , This is Kaushik Reddy again. After a long work, I would like to introduce you to my idea proposal for the (Wikimedia) GSoC '19. Here is it: 1) Building an animation to dynamically create popups overlapped on a geographical map using a real-time API from Wikimedia. I had found the root of this in here( I have gone through it a bit): https://meta.m.wikimedia.org/wiki/Research:Data I would like to work this out as my Google summer of code-19 project for Wikimedia. May I know who good is it? Also, feel free to comment on this. With regards, Kaushik.

1 0

CI updates: Quibble on Stretch, and Headless Chrome 71
by Krinkle 10 Feb '19

10 Feb '19

TL;DR: * MediaWiki jobs now run on the same Debian OS version as wmf-production, which makes make the wmf-quibble PHPUnit tests even more useful. * The QUnit tests for MediaWiki repos now use Headless Chrome. (For other repos, this was done last year.) ## Quibble HHVM now on Debian Stretch Quibble is the Jenkins runner for MediaWiki-related repositories. Its variants for php70 through php73 were already based on Debian 9 ("Stretch"), with a recent Chromium version (Thanks Legotkm and Hashar!). The HHVM variant, however, was still on Debian 8 ("Jessie"). This caused a number of side effects: * wmf-quibble-hhvm no longer matched wmf production (due to a different operating system version). This could cause subtle differences in backend behaviour to miss problems in our testing. * Debian 8 provided an outdated version of Chromium (version 57), which is no longer supported by Google, and actually had problems with its PKI-NSS storage layer. These were fixed in later versions of Chromium. * The Chromium versions differed between the hhvm and php7 jobs, because the latter is provided by Debian 9 with Chrome 69. This could cause subtle bugs that affected one job but not the other. It also precluded use of Headless Chrome. I've ported the Docker image for quibble-*-hhvm to Debian 9. The tests now match wmf production, and our QUnit tests and browser tests now consistently run against the same (recent) version of Chrome. Apart from one test failure in the Navigation Timing extension, [1] all gated repositories were verified and still pass. ## Headless Chrome Since the stable release of Chromium 59 in 2017, this browser now comes with a headless mode that starts and runs significantly faster than the desktop variant. Most of our non-mediawiki repositories only had Jenkins jobs using the newer Debian 9 (with Chrome 69), and thus were already enjoying the speed of Headless Chrome. Now that quibble-hhvm is upgraded to Debian 9, which comes with Chrome 69, the MediaWiki tests can use Headless Chrome as well. [2] I've also rebuild the quibble jobs again with another round of Debian 9 package updates, which further upgrades Chromium from 69 to 71. Happy testing! -- Timo Tijhof [1] https://phabricator.wikimedia.org/T215714 – 1 test failing within ext.navigationTiming (temporary disabled). [2] https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/486188/ – build: Use Headless Chrome for karma-qunit tests.

1 0

TechCom Radar 2019-02-06
by Kate Chapman 08 Feb '19

08 Feb '19

Hi All, Here are the minutes from this week's TechCom meeting: * On Last Call ending 20 February 1pm PST(21:00 UTC, 22:00 CET) Wikibase Front-End Architecture <https://phabricator.wikimedia.org/T213318> with the caveat that this is an opportunity for Wikidata to experiment with this approach while TechCom discusses out to do Front End Architecture in a more universal/organized way. Also noting this introduces a circular dependency that should be resolved at some point. * IRC Meeting 11pm PST February 13 (February 14 07:00 UTC, 08:00 CET) in #wikimedia-office Use Github login for mediawiki.org - <https://phabricator.wikimedia.org/T215046> * Reopened: RFC: Multiblocks - let admins create multiple, overlapping blocks on a single user <https://phabricator.wikimedia.org/T202673> because it was closed due to lack of resourcing rather than it being something that would never potentially be implemented. You can also find our meeting minutes at <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> See also the TechCom RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. If you prefer you can subscribe to our newsletter here <https://www.mediawiki.org/wiki/Newsletter:TechCom_Radar> Thanks, Kate -- Kate Chapman Senior Program Manager, Core Platform Wikimedia Foundation kchapman(a)wikimedia.org

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l February 2019