Wikitech-l April 2019

wikitech-l@lists.wikimedia.org

69 participants
75 discussions

Re: [Wikitech-l] TechCom Radar 2019-04-10
by Daniel Kinzler 12 Apr '19

12 Apr '19

Am 12.04.19 um 05:18 schrieb David Sharpe: > I think there was an extra text paste affecting this portion of the document: > > “Motivation: Motivation: These principles aim at the /equity/ goal set by > the /Movement Strategy Outcomes/ and reflected in the Wikimedia > Foundation's /Goals and Priorities/: /"Modernize our product experience/", > particularly by /"integrating content from Commons, Wikidata, Wikisource and > other projects into Wikipedia”/." Double motivation :) fixed, thank you. -- Daniel Kinzler Principal Software Engineer, Core Platform Wikimedia Foundation

1 0

[CfP] DBpedia meeting || May 23rd, 2019 || Leipzig
by Sebastian Hellmann 12 Apr '19

12 Apr '19

Dear all, We are happy to announce that the 13th DBpedia Community Meeting will be held in Leipzig, Germany on 23rd of May, 2019. DBpedia will be part of the Language, Data and Knowledge conference (LDK). This new biennial conference series aims at bringing together researchers from across disciplines. Further information on the conference program and its associated events can be found here: http://2019.ldk-conf.org/. * Highlights * - Keynote #1: Making Linked Data Fun with DBpedia by Peter Haase, metaphacts - Keynote #2: From Wikipedia to Thousands of Wikis – The DBkWik Knowledge Graph by Heiko Paulheim, University of Mannheim - DBpedia Association hour - DBpedia Showcase Session * Quick Facts * - Web URL: http://wiki.dbpedia.org/meetings/Leipzig2019 - When: May 23rd, 2019 - Where: Mediencampus Villa Ida, Poetenweg 28, 04155 Leipzig - Call for Contribution: Submit your proposal in our form https://goo.gl/forms/pThmvkvoK8jR5gFM2 - Registration: You need to buy a ticket via https://www.eshop.sachsen.de/infai/infai_store_english/ * Side Event * The Thinktank and Hackathon “Artificial Intelligence for Smart Agriculture” is part of the DBpedia meeting. The activity is supported by the projects DataBio, Bridge2Era as well as CIAOTECH/PNO. The goal of the thinktank & hackathon is to build new ideas and small tools, which are able to demonstrate the use auf AI within the agricultural domain and a sustainable bioeconomy. Especially, the use and impact of linked data for AI components will be one part of the event. Further discussions about future collaborations and ideas of the future of AI-based Smart Agriculture will be held. Please submit your ideas and projects here: https://docs.google.com/forms/d/e/1FAIpQLSfXD4_shiDkiHrMSwtEbEzl746oAd-GAAm… We are looking forward to meeting you in Leipzig! Kind regards Your DBpedia Association

1 0

TechCom Radar 2019-04-10
by Daniel Kinzler 11 Apr '19

11 Apr '19

Hi All, Here are the minutes from this week's TechCom meeting: * Older task turned into RFC for discussion: Create temporary accounts for anonymous editors. <https://phabricator.wikimedia.org/T133452> * Updated: Re-evaluate librsvg as SVG renderer on Wikimedia wikis: resvg is now available in Debian unstable, perhaps experiments with thumbor could start. <https://phabricator.wikimedia.org/T40010> * Last Call until April 24: Establish Architecture Principles as a policy <https://phabricator.wikimedia.org/T220657> * New request for guidance: Introduce PageIdentity to be used instead of Title. <https://phabricator.wikimedia.org/T208776> * First TechCom office hour on IRC next week, April 17, 2pm PDT (21:00 UTC, 23:00 CEST). We'll be on #wikimedia-officem, come and ask us anything! 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 _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

1 0

Last Call for comments on the Architecture Principles
by Daniel Kinzler 11 Apr '19

11 Apr '19

After a year of drafting and discussions, TechCom is putting its proposed Architecture Principles on last call, to be adopted as official policy. This policy will apply to all engineering endeavors of the Wikimedia foundation, and is intended to guide all engineering decisions, great and small. This is a big deal, but it's not intended to be a revolution. The Architecture Principles mostly codify things that have long been established practice, or have long been agreed on to be desirable. Not by everybody, but by rough consensus. We did our best to provide opportunities for input and feedback, and tried hard to incorporate and consolidate. The Architecture Principles are a statement of value of the engineers of Wikimedia, as represented by TechCom. They mean a great deal to us. We hope you will find them useful when evaluating ideas and plans. They are intended as a guide that ensures coherence, a tool that helps us build better software together. You can find the draft at <https://www.mediawiki.org/wiki/Wikimedia_Engineering_Architecture_Principles>. You can find past discussion on the talk page, but please put any new comments on the phabricator ticket where we track the last call, as required by the RFC process: <https://phabricator.wikimedia.org/T194911>. The last call is open until April 24. If no major issues are raised and remain unresolved by that time, the draft will be accepted as policy. But keep in mind that the principles are not intended to be set in stone. They are derived from the strategic goals and product priorities, from past experience and from current constraints. When these things change, the principles should change. -- Daniel Kinzler Principal Software Engineer, Core Platform Wikimedia Foundation

1 1

Scrum of scrums/2019-04-10
by Željko Filipin 11 Apr '19

11 Apr '19

Hi, for HTML version see https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-04-10 Željko -- = 2019-04-10 = == Callouts == * SRE reminds everyone Thursday maintenance on s3 wikis databases: https://phabricator.wikimedia.org/T220080 ** We're looking for 1-2 backup facilitators, in case the facilitator can't make it to the meeting == Audiences == === Contributors === ==== Community Tech ==== * Blocked by: * Blocking: * Updates: ** Event Metrics ends this week. We are polishing bugs now. ** Working with TechCom on this task about delayed jobs and job queues: https://phabricator.wikimedia.org/T218812 ** Pediapress is committed to helping with PDF generation for Wikisource ==== Anti-Harassment Tools ==== * Blocked by: * Blocking: * Updates: ** Enabled Partial Blocks on French and Polish wikis ** Refactoring Blocks with the help of TechCom ==== Editing ==== * Blocked by: * Blocking: * Updates: ==== Growth ==== * Blocked by: * Blocking: * Updates: ==== Language ==== * Blocked by: * Blocking: * Updates: === Readers === ==== iOS native app ==== * Blocked by: * Blocking: * Updates: ** 6.2.1 released ( https://phabricator.wikimedia.org/tag/ios-app-v6.2.1-beluga-on-stilts/) *** find & replace *** syntax highlighting switch *** clear formatting *** bug fixes ** 6.3 in development ( https://phabricator.wikimedia.org/tag/ios-app-v6.3-lobster-on-a-motorcycle/) *** talk pages *** link insertion wizard *** media insertion wizard *** link previews *** bug fixes ==== Android native app ==== * Blocked by: * Blocking: * Updates: ** Released Beta version of Suggested Edits (automatic suggestions for adding/translating Wikidata descriptions) ==== Readers Web ==== * Blocked by: Release Engineering: https://phabricator.wikimedia.org/T199939. We are not blocked right now but will be blocked in a couple of weeks - basically web team needs a way to enable feature flags for browser tests. We write browser tests for features that are not released yet. This works in the Ruby framework but not Node.js. * Blocking: * Updates: ** Summary: (same as last week) technical planning for next year, continuing advanced mobile contributions features and the MobileFrontend architecture investment project. ** Responsive website (MinervaNeue / MobileFrontend): *** Advanced mobile contributions https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions **** It should be possible to view the desktop history page in AMC T219874 **** Skin Contributions and History pages in Minerva for consistency with their mobile replacements T219349 **** AMC Navigation - add new links to main menu with click tracking T216152 **** No way to reach the editable version of a page when viewing the most recent mobile diff T200969 **** Add secondary page actions submenu in AMC mode T216418 *** Invest in the MobileFrontend & MinervaNeue frontend architecture https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFro… **** Inline Hogan templates in mobile.startup T219838 **** Replace Nearby inheritance with composition T217814 **** Refactor NotificationsOverlay T219036 **** Refactor TalkSectionAddOverlay T217102 *** CI tests disabled: Steps that require login are disabled and should be restored T219920 *** Minerva Ruby and Node.js browser tests running side by side T190710 *** ExternalGuidance extension review and support *** Miscellaneous bug fixes and maintenance T97891 T159475 T218809 T219846 ** Desktop website (Popups) *** Popups https://www.mediawiki.org/wiki/Page_Previews **** WMDE reference previews review and support ** Planning *** MobileFrontend & MinervaNeue frontend architecture planning for next fiscal year ==== Readers Infrastructure ==== * Blocked by: * Blocking: * Updates: ** (mainly interesting for apps and web team): *** Base CSS output is now decoupled from live ResourceLoader requests. We now only update the CSS on demand. *** Fixed issue with missing icon for external links. *** Added Wikibase entity ID for image files (T219667) ** Maps: OS stretch migration is not stalled anymore, maps2003.codfw is migrated and maps200[1-2] are on their way ==== Multimedia ==== * Blocked by: ** Release Engineering: jenkins job to run core tests against beta.commons, see https://phabricator.wikimedia.org/T220621 * Blocking: * Updates: still trying to get depicts release out the door :( ** mostly working on testing this week in advance of releaes ==== Parsing ==== * Blocked by: * Blocking: * Updates: ==== UI Standardization ==== * Blocked by: * Blocking: * Updates: ** Improved mobile font stack successfully rolled-out 🎉 https://m.mediawiki.org/wiki/Design/Projects/Improve_mobile_reading_experie… ** Continuing collaboration with Jon Robson on AMC work, *** HistoryAction to OOUI (aftermath addressing community feedback) *** preparing Special:Contributions for the same https://phabricator.wikimedia.org/T117736 ** OOUI v0.31.3 was released last week after ScrumofScrums https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v… *** SelectFileInputWidget: Support multiple files to upload *** Infusion reflow fixes on various widgets *** DropdownWidget layout consistency fixes across browsers dating back to IE 8 == Technology == === Analytics === * Blocked by: * Blocking: * Updates: === Cloud Services === * Blocked by: * Blocking: * Updates: === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** Payments-wiki is back on mediawiki 1.31, patch to update tests in review ** Deployed first version of fancy opt-in page, working on refinements ** Continuing work on decoupling last direct link between payments-wiki and civi DB ** Prepping latest CiviCRM point upgrade for deploy ** Adapting payments forms to make a better experience for donors using 3D Secure authentication === Core Platform === * Blocked by: * Blocking: ** (Core Platform, Parsing) Undefined index: june in DateFormatter.php (makeIsoMonth) https://phabricator.wikimedia.org/T220563 * Updates: ** Epic for RESTBase Split https://phabricator.wikimedia.org/project/view/3918/ ** Updates to RESTBase UI ** REST API testing spec https://etherpad.wikimedia.org/p/api-tests-yaml ** decommissionning some RESTBase Cassandra servers === Performance === * Blocked by: ** Traffic: X-Wikimedia-Debug fatal hijacked by Varnish https://phabricator.wikimedia.org/T217846 ** CPT: CR on avoiding double parsing during save https://gerrit.wikimedia.org/r/c/mediawiki/core/+/470099/ ** CPT: Input from Tim on Excimer config https://phabricator.wikimedia.org/T176916#5064425 ** CPT: CR on Graph extension multi-DC caching https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Graph/+/493628/ * Blocking: * Updates: ** Fixed issue in upload stash (manifested itself in UploadWizard flickr import, but could be also elsewhere) related to Swift container permissions ** Blog post about upcoming Element Timing for Images API, very useful metric in the future (currently an Origin Trial in Chrome): https://phabricator.wikimedia.org/phame/post/view/157/evaluating_element_ti… === Release Engineering === * Blocked by: * Blocking: ** Readers Web: https://phabricator.wikimedia.org/T199939. (see reading web section for more context) ** Search Platform: need help with https://phabricator.wikimedia.org/T220046 (setting up gerrit account) ** Multimedia: jenkins job to run core tests against beta.commons, see https://phabricator.wikimedia.org/T220621 * Updates: ** Train Health *** Last week: 1.33.0-wmf.24 - https://phabricator.wikimedia.org/T206678 **** Finished a few day late (Monday instead of Thursday) but in time for this week's train *** This week: 1.33.0-wmf.25 - https://phabricator.wikimedia.org/T206679 **** Some problems, not blocked *** Next week: 1.34.0-wmf.1 - [NEEDS TASK] === Research === * Blocked by: * Blocking: * Updates: ** Published a blog post on the Citation Needed project: https://wikimediafoundation.org/2019/04/03/can-machine-learning-uncover-wik… ** Annual and mid-term plan ** Wikimania and Wikimedia Hackathon planning ** Ongoing talks about section alignment and ContentTranslation tool integration === Scoring Platform === * Blocked by: * Blocking: * Updates: === Search Platform === * Blocked by: RelEng: need help with https://phabricator.wikimedia.org/T220046 (setting up gerrit account) * Blocking: * Updates: ** All relevant extensions & configs migrated to WikibaseCirrusSearch, removing old code next: https://phabricator.wikimedia.org/T190022 ** Highlighting with inlabel: fixed, waiting for deploy https://phabricator.wikimedia.org/T217809 ** Completed review of language identification status on wikis: https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Review_of_Language_I… *** Subordinate tasks filed in https://phabricator.wikimedia.org/T174116 ** Added icinga checks for ES lags: https://phabricator.wikimedia.org/T219601 ** Fixed some job queue timeouts: https://phabricator.wikimedia.org/T219234 ** Fixed job queue error with ElasticaWrite: https://phabricator.wikimedia.org/T124196 ** Working on cleaning up deprecations after ES6 upgrade: https://phabricator.wikimedia.org/T218994 ** Setting up CloudElastic servers: https://phabricator.wikimedia.org/T214921 ** Preparing for Haystack conference: https://phabricator.wikimedia.org/T220519 ** Working on WDQS performance improvements: https://phabricator.wikimedia.org/T217897 === Security === * Blocked by: * Blocking: * Updates: ** https://phabricator.wikimedia.org/T220242: concept review, in Progress ** https://phabricator.wikimedia.org/T220043: concept review, in Progress ** https://phabricator.wikimedia.org/T219289: concept review, in Progress ** https://phabricator.wikimedia.org/T216419: in Progress, to be completed mid-April ** https://phabricator.wikimedia.org/T217289: TBD ** https://phabricator.wikimedia.org/T216692: TBD ** https://phabricator.wikimedia.org/T201492: TBD ** https://phabricator.wikimedia.org/T103011: TBD === Site Reliability Engineering === * Blocked by: ** None * Blocking: ** None * Updates: * SRE reminds everyone Thursday maintenance on s3 wikis databases: https://phabricator.wikimedia.org/T220080 == TechComm == * Blocked by: * Blocking: * Updates: ** Updates to the draft Architecture Principles have been made based on feedback: https://www.mediawiki.org/w/index.php?title=Wikimedia_Engineering_Architect… == Wikidata == * Blocked by: * Blocking: * Updates: ** Wikibase Schema, a.k.a. Shape Expressions implementation finished, security review pending: https://phabricator.wikimedia.org/T216692 ** Mobile Termbox progresses: implementing editing of existing labels, description and aliases ** Termbox Server Side Rendering service pending security review: https://phabricator.wikimedia.org/T216419 ** wb_terms trailblaze - discussing possible migration plans with DBAs https://phabricator.wikimedia.org/T220230 == German Technical Wishlist == * Blocked by: * Blocking: * Updates: == SoS Meeting Bookkeeping == * Blocked by: * Blocking: * Updates: ** We're looking for 1-2 backup facilitators, in case the facilitator can't make it to the meeting

2 2

Re: [Wikitech-l] [Wikidata] URL shortener for the Wikimedia projects will be available on April 11th
by Amir Sarabadani 11 Apr '19

11 Apr '19

Hey, This is live now, you can use it in https://meta.wikimedia.org/wiki/Special:UrlShortener Best On Wed, Apr 3, 2019 at 2:14 PM Léa Lacroix <lea.lacroix(a)wikimedia.de> wrote: > *(apologies for crost-posting - feel free to share this announcement in > your communities)* > > Hello all, > > Having a service providing short links exclusively for the Wikimedia > projects is a community request that came up regularly on Phabricator > <https://phabricator.wikimedia.org/T44085> or in community discussions > <https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Reading/Crea…>. > > > After a common work of developers from the Wikimedia Foundation and > Wikimedia Germany, we are now able to provide such a feature, it will be > enabled on April 11th on Meta. > *What is the URL Shortener doing?* > > The Wikimedia URL Shortener is a feature that allows you to create short > URLs for any page on projects hosted by the Wikimedia Foundation, in order > to reuse them elsewhere, for example on social networks or on wikis. > > The feature can be accessed from Meta wiki on the special page > m:Special:URLShortener > <https://meta.wikimedia.org/wiki/Special:URLShortener> (will be enabled > on April 11th). On this page, you will be able to enter any web address > from a service hosted by the Wikimedia Foundation, to generate a short URL, > and to copy it and reuse it anywhere. > > The format of the URL is w.wiki/ followed by a string of letters and > numbers. You can already test an example: w.wiki/3 redirects to > wikimedia.org. > *What are the limitations and security measures?* > > In order to assure the security of the links, and to avoid shortlinks > pointing to external or dangerous websites, the URL shortener is restricted > to services hosted by the Wikimedia Foundation. This includes for example: > all Wikimedia projects, Meta, Mediawiki, the Wikidata Query Service, > Phabricator. (see the full list here > <https://meta.wikimedia.org/wiki/Wikimedia_URL_Shortener>) > > In order to avoid abuse of the tool, there is a rate limit: logged-in > users can create up to 50 links every 2 minutes, and the IPs are limited to > 10 creations per 2 minutes. > *Where will this feature be available?* > > In order to enforce the rate limit described above, the page > Special:URLShortener will only be enabled on Meta. You can of course create > links or redirects to this page from your home wiki. > > The next step we’re working on is to integrate the feature directly in the > interface of the Wikidata Query Service, where bit.ly is currently used > to generate short links for the results of the queries. For now, you will > have to copy and paste the link of your query in the Meta page. > *Documentation and requests* > > - If you have any question or requests, feel free to leave a comment > under this Phabricator task <https://phabricator.wikimedia.org/T44085> > - The user documentation is available here > <https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_URL_Shortener>: > please help us to translate it in your language! > - See also the technical documentation of the extension > <https://www.mediawiki.org/wiki/Extension:UrlShortener> > > Thanks a lot to all the developers and volunteers who helped moving > forward with this feature, and making it available today for everyone in > the Wikimedia projects! > -- > Léa Lacroix > Project Manager Community Communication for Wikidata > > Wikimedia Deutschland e.V. > Tempelhofer Ufer 23-24 > 10963 Berlin > www.wikimedia.de > > Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. > > Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg > unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt > für Körperschaften I Berlin, Steuernummer 27/029/42207. > _______________________________________________ > Wikidata mailing list > Wikidata(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikidata > -- Amir

1 0

s3 primary db master failover on Thursday 10th April 05:00AM UTC
by Manuel Arostegui 10 Apr '19

10 Apr '19

Hello, Due to hardware malfunction on the current s3 database primary master (T219115) we need to failover it to a different host. We are going to do this on Thursday 10th at 05:00 AM UTC, and we have requested a 30 minutes window (T220080) as we have to go read only for all the wikis living on s3 (P7994). Impact: Writes will be blocked, reads will remain unaffected. Time: 05:00AM UTC - 05:30 AM UTC (we do not expect to use the full 30 minutes window). Communication will happen at #wikimedia-operations If you are around at that time and want to help with the monitoring, please join us! Thanks

2 4

MediaWiki 1.33 branch announcement
by Greg Grossmeier 10 Apr '19

10 Apr '19

Hello! We are beginning the process of working on the 1.33.0 release of MediaWiki. The release is currently scheduled for May 2019. We created the REL1_33 branch this week (aligned with the final Wikimedia alpha, 1.33.0-wmf.25), and will be generating the first release candidate soon, so this means it's now "pencils down". If you have any open Phabricator tasks tagged with mw-1.33-release [0], please check to see if they are indeed blockers for the release. If not, please remove the tag from them. Conversely, if there are any blockers that are not tagged with mw-1.33.release, please tag them. Please feel free to reach out to me if you have any questions about this. We will be in the normal patch master + backport process from now until the release in May. Thanks, Greg [0] https://phabricator.wikimedia.org/tag/mw-1.33-release/ -- Greg Grossmeier Release Team Manager

1 0

Uploading new versions of other people's patches to gerrit
by Isarra Yos 10 Apr '19

10 Apr '19

This seems to be broken, or something. It's causing problems for collaboration. Please fix. -I

7 13

Discovery Weekly Update for the week starting 2019-03-25
by Chris Koerner 09 Apr '19

09 Apr '19

Greetings, This is the weekly update from the Search Platform team for the week starting 2019-03-25 and 2019-04-01. As always, feedback and questions are welcome. == Discussions == === Search === * ElasticSearch upgrade to v6: ** incident [0] *Trey finished a deep dive into the performance of language identification for cross-wiki searching [1] (example [2]) and punctuation-related problems, and discovered things are working pretty well overall, but the Chinese language model is a bit off. * Erik noticed that the inlabel / incaption keywords should highlight the label/caption but were not [3] * David worked on fixing an error code that Elasticsearch 6 nested_path and nested_filter are deprecated [4] and _retry_on_conflict was deprecated [5] * We worked on migrating mjolnir to stdout/syslog/cee logging output [6] * The team worked on upgrade to elasticsearch 6.5.4 for cirrus / codfw (specifically) [7] and for eqiad [8] * Erik worked on the implementation and testing of glent m0 integration with wmf infrastructure [9] * David did a lot of work to update the mw-config to use the psi&omega elastic clusters [10] * David found that the auto_generate_phrase_queries is deprecated and ineffective [11] * The team fixed an old bug where we were getting fatal errors - "cannot perform this operation with arrays" from CirrusSearch/ElasticaWrite (using JobQueueDB) [12] * Gehel worked to make spicerack more robust when unfreezing writes to elasticsearch / cirrus [13] as well as creating a cookbook to reset frozen write state on elasticsearch / cirrus [14] * Stas moved WikibaseLexeme search code to WikibaseLexemeCirrusSearch extension [15] * We noticed that Elasticsearch indices went read-only, causing a huge lag [16] * We also saw where search exceptions handling was printing response information on the screen [17] * The team fixed an issue where mwgrep was not working [18] * We also fixed an issue where Elasticsearch 6 needed to silence deprecation warnings to avoid logspam [19] * We needed to create an extra elasticsearch clusters in the beta cluster [20] * We also needed some alerts so we know if mjolnir starts misbehaving [21] * We also converted check_elasticsearch.py icinga plugin to py3 [22] * We needed to start using local nginx reverse proxy for connections reuse [23] * The version of curator that we currently use (5.2.0) isn't compatible with elasticsearch 6. Which causes issues in a few cron on logtash servers (see blelow). Version 5.6.0 supports both elasticsearch 5 and 6.....so...we updated it [24] * We also did some cleanup of the reprepro configuration for elasticsearch-curator [25] * Getting a centralized way to inspect the content of the search profiles might be helpful when investigating search behaviors. In the same vein as other dump debug APIs (mapping/settings/cirrusdoc) David suggested that we should add a new simple API to dump the profiles (cirrus-profiles-dump) [26] * David also found that a call to a member function toArray() on a non-object (null) in vendor/ruflin/elastica/lib/Elastica/Client.php:736 and fixed it [27] [0] https://wikitech.wikimedia.org/wiki/Incident_documentation/20190327-elastic… report [1] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Review_of_Language_I… [2] https://en.wikipedia.org/w/index.php?search=%D0%93%D0%B0%D1%80%D1%80%D0%B8+… [3] https://phabricator.wikimedia.org/T217809 [4] https://phabricator.wikimedia.org/T219266 [5] https://phabricator.wikimedia.org/T219265 [6] https://phabricator.wikimedia.org/T218833 [7] https://phabricator.wikimedia.org/T218878 [8] https://phabricator.wikimedia.org/T218879 [9] https://phabricator.wikimedia.org/T218164 [10] https://phabricator.wikimedia.org/T210381 [11] https://phabricator.wikimedia.org/T219267 [12] https://phabricator.wikimedia.org/T124196 [13] https://phabricator.wikimedia.org/T219640 [14] https://phabricator.wikimedia.org/T219638 [15] https://phabricator.wikimedia.org/T216206 [16] https://phabricator.wikimedia.org/T219364 [17] https://phabricator.wikimedia.org/T216959 [18] https://phabricator.wikimedia.org/T219162 [19] https://phabricator.wikimedia.org/T219269 [20] https://phabricator.wikimedia.org/T213940 [21] https://phabricator.wikimedia.org/T214494 [22] https://phabricator.wikimedia.org/T215439 [23] https://phabricator.wikimedia.org/T215491 [24] https://phabricator.wikimedia.org/T218991 [25] https://phabricator.wikimedia.org/T216235 [26] https://phabricator.wikimedia.org/T218682 [27] https://phabricator.wikimedia.org/T217402 ---- Subscribe to receive on-wiki (or opt-in email) notifications of the Discovery weekly update. https://www.mediawiki.org/wiki/Newsletter:Discovery_Weekly The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner (he/him) Community Relations Specialist Wikimedia Foundation

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 April 2019