Wikitech-l November 2019

wikitech-l@lists.wikimedia.org

53 participants
67 discussions

FOSDEM 2020 web performance devroom CfP
by Gilles Dubuc 26 Nov '19

26 Nov '19

We (the Wikimedia Performance Team <https://www.mediawiki.org/wiki/Wikimedia_Performance_Team>) are hosting a devroom at FOSDEM 2020 <https://fosdem.org/2020/>. We are still looking for talk proposals on the topic of Web Performance, with a focus on FLOSS, open standards and research. Deadline is December 2. Details here: https://github.com/wikimedia/fosdem20-web-performance-cfp

1 0

s7 primary master switchover (read-only required) 26th Nov 06:00 AM UTC
by Manuel Arostegui 26 Nov '19

26 Nov '19

Hello, We have requested a 30 minutes read-only window for s7 (T238046) for the 26th November from 06:00-06:30 AM UTC to switchover that section primary database master (T238044) db1062 is an old host and out of warranty that will be decommissioned (T217396). The new master will be db1086 We are going to do this on Tuesday 26th Nov from 06:00 to 06:30 AM UTC (we do not expect to use the 30 minutes window, if everything goes as expected). Impact: Writes will be blocked on the following wikis: arwiki cawiki eswiki fawiki frwiktionary hewiki huwiki kowiki metawiki rowiki ukwiki viwiki Reads will remain unaffected. This also includes centralauth database, which means some operations might fail during the read-only period, such as: GlobalRenames, Changing/Confirming emails, logging into new wikis, password changes... Communication will happen at #wikimedia-operations If you are around at that time and want to help with the monitoring, please join us! Thanks

1 2

This Week in Logspam (Thanksgiving Edition)
by Brennen Bearnes 25 Nov '19

25 Nov '19

Hi all, A high volume of error messages in production logs can make it hard to glance at error logs after a deployment and reason about the deployment's impact.[0] This recurring mail is part of an ongoing effort to reduce log noise. At present I'm aware of three unresolved-but-tracked issues which are causing a fair amount of noise: * https://phabricator.wikimedia.org/T143756 ** UnresolvedRedirectException in EntityAccessor::getEntity (scribunto) ** ~8000 occurrences today * https://phabricator.wikimedia.org/T226751 ** PHP error "non well formed numeric value encountered" from FormatMetadata->formatCoords ** ~600 occurrences today * https://phabricator.wikimedia.org/T239165 ** PHP Warning: count(): Parameter must be an array or an object that implements Countable in WikibaseMediaInfo ** ~120 occurrences today As ever, help in eliminating these errors from production logs is greatly appreciated. As a procedural note, I'm sending this early in the week due to the Thanksgiving holiday. We'll be releasing 1.35.0-wmf.8 to group 0 tomorrow (Tuesday) and then pausing there until 2019-12-04. [0]. https://wikitech.wikimedia.org/wiki/Deployments/Holding_the_train#Logspam -- Brennen Bearnes (he/him) Release Engineering Wikimedia Foundation

1 0

Cloud VPS users, please claim your projects
by Andrew Bogott 25 Nov '19

25 Nov '19

Every year or so the Cloud Services team tries to identify and clean up unused projects and VMs. We do this via an opt-in process: anyone can mark a project as 'in use,' and that project will be preserved for another year. I've created a wiki page the lists all existing projects, here: https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2019_Purge If you are a VPS user, please visit that page and mark any projects that you use as {{Used}}. Note that it's not necessary for you to be a project admin to mark something -- if you know that you're currently using a resource and want to keep using it, go ahead and mark it accordingly. If you /are/ a project admin, please take a moment to mark which VMs are or aren't used in your projects. When December arrives, I will shut down and begin the process of reclaiming resources from unused projects. If you think you use a VPS project but aren't sure which, I encourage you to poke around on https://tools.wmflabs.org/openstack-browser/ to see what looks familiar. Worst case, just email cloud(a)lists.wikimedia.org with a description of your use case and we'll sort it out there. Exclusive toolforge users are free to ignore this task. Thank you! -Andrew and WMCS team

2 4

Google Code-in 2019 starts in one week (and we need more tasks)
by Andre Klapper 24 Nov '19

24 Nov '19

Wikimedia is one of the organizations in Google Code-in (GCI) 2019! GCI starts on December 02 and runs for seven weeks. It's a contest for 13-17 year old students working on small tasks and an opportunity to let new contributors help with tasks on your To-Do list! :) PLEASE CONSIDER BECOMING A MENTOR: 1. Go to https://www.mediawiki.org/wiki/Google_Code-in/2019 and add yourself to the mentor's table. 2. Get an invitation email to register on the contest site. ...AND MENTOR SMALL TASKS: * Do your docs on your wiki need some improvements? * Does your template or gadget code needs some updates? * Do you have small and self-contained bugs you'd love to get fixed? * Does your UI have small design issues? * Do your old bugs welcome some testing? We need tasks in the following areas: code, outreach/research, documentation/training, quality assurance, user interface/design. See https://www.mediawiki.org/wiki/Google_Code-in/Mentors Looking for task ideas? Check the good_first_bugs in Phabricator: https://phabricator.wikimedia.org/maniphest/query/agR7xiuqv_bc/#R Any questions? Feel free to ask the org admins at google-code-in-admins(a)lists.wikimedia.org - we are happy to help! Thank you for your help broadening our contributor base! andre -- Andre Klapper (he/him) | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/

1 0

Help on creating a new extension
by Sohom Datta 24 Nov '19

24 Nov '19

Hi guys, I'm Sohom Datta. I recently decided to create a draft for an hypothetical extension ProtectionIndicator, which will add a protection icon on the top of every protected page. I did this primarily out of my own interest in getting familiar with the code-base of MediaWiki. I've hosted all the code I have written (still unfinished) in this github repository <http://github.com/sohomdatta1/ProtectionIndicator>. I'd like some guidance on how to implement the unfinished parts of the extension especially the integration with FlaggedRevs and the addition of a log entry to a popup ( Details are there in the readme.md of the repo) . Also any feedback on my code would also be very good. Also, it would be great if somebody could guide me on how to make this a official extension someday. Regards, Sohom Datta

5 6

Rename Phabricator task priority "Normal" to "Medium"
by Andre Klapper 23 Nov '19

23 Nov '19

Hello, hello! Do you often spend time prioritizing tasks in Phabricator? Then please feel invited to share your opinion in https://phabricator.wikimedia.org/T228757 (Reminder: "Opinion" implies "arguments", not a short "Like!"/"Don't like!" comment - please use tokens for that! :P ) Do you have more opinions to share about things in Phabricator? * There is also a proposal to merge the "Low" and "Lowest" priority field values in https://phabricator.wikimedia.org/T228759 * There is also a proposal to nag (and then at some point unassign) people assigned to open tasks for years without progress in https://phabricator.wikimedia.org/T228575 Thanks, your personal Phabricator bot ("andre") -- Andre Klapper (he/him) | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/

2 1

Phabricator Maintenance bot source code
by Amir Sarabadani 22 Nov '19

22 Nov '19

Hey, Today finally I was able to polish the code for phabricator maintenance bot [1]. In case you don't know, it's a bot that do cleanups in phabricator for cases Herald is unable to handle them (like moving tasks in columns). This bot probably has been spamming you with emails. I also made it practically completely automatic (You merge the pull request, you will see its effect one hour later). So pull requests are more than welcome. You can also simply add some rules for the bot to move tickets in columns. If you want to help in maintaining the tool. Send me a message and I will add you to the toolforge tool. Thanks! [1]: https://github.com/Ladsgroup/Phabricator-maintenance-bot -- Amir (he/him)

1 0

Scrum of scrums/2019-11-20
by Željko Filipin 22 Nov '19

22 Nov '19

Hi, for HTML version see https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-11-20 Željko -- = 2019-11-20 = == Callouts == ** SRE: *** DBAS [general update] Upcoming s1 (enwiki) database master switch 14 Nov: [[phab:T234800]] [will imply a small read only window] *** Requesting follow-up from Scoring team [[phab:T233448#5638765]] *** Requesting follow-up from Releng team [[gerrit:479139]] ** Release Engineering: no train because of team offsite == Product == === iOS native app === * Blocked by: **Core Platform ***release wikidiff2 to get section titles from compare endpoint ***counts endpoint limit increases ***minor count endpoint failing ( https://en.wikipedia.org/w/rest.php/v1/page/Barack_Obama/history/counts/min… ) * Updates: **6.5 wrapping up bugs/development - [[phab:project/view/4245]] ***aiming to be in public beta Friday (11/22) === Android native app === * Updates: ** Our major release is all set to go out the door.: [[phab:project/view/4123]] *** Fundraising banner is ready and in review. *** We have re-started work on integration with mobile-html endpoint. === Product Infrastructure === * Updates: * Patches for client-side error logging and EventLogging client improvements * Security review followups for MachineVision * Reviewing MCS overhaul patches * Wikifeeds ** Removed frwiki from supported TFA wikis due to [[phab:T237790]] ** Patch in review for upgrading to Node 10 -- just need confirmation from CPT that this won’t cause any problems === Structured Data === * Blocked by: ** WMDE/Wikidata: review of [[gerrit:548734]] ([[phab:T222497]]) * Blocking: ** Search Platform: Data dumps for SDC: [[phab:T221917]] === Parsing === * Blocked by: ** deployment recipe issues need resolving before we do additional live traffic deploys ([[phab:T238685]] and [[phab:T238748]]) ** (soft blocker) still working to get all parsoid clients tested against parsoid/php (Content translation and flow) * Updates: ** parsoid/php is on testwiki -- see wikitech-l mail from y'day === Inuka === * Updates: ** PageViews instrumentation: [[phab:T238029]] == Technology == === Fundraising Tech === * Updates: ** CiviCRM *** More tweaks to how we import data from our bulk mailing provider *** Changes to our custom drupal code to accommodate using a read-only database connection for some requests. *** Still working on button to send end-of-year summary receipt on demand [[phab:T221271]] ** CentralNotice *** Trying to understand a few more oddities in the new EventLogging data pipeline. For example, how are we getting client-side FundraiserLandingPage events without corresponding server-log pageviews? [[phab:T236835#5670862]] ...see the section "Explaining orphaned events in new logs" *** Finishing up initally-contractor-written feature to extend geotargeting to regions smaller than countries. [[phab:T226438]] === Core Platform === * Blocking: ** Potentially Wikidata/WMDE: Mentioned 2 times in SoS already with no result: In the Data Bridge work (editing Wikidata items from Wikipedia) we have encountered problems with Special:EntityData serving stale (old) data. The problem is quite old: [[phab:T128486]]. We are looking for a team/person with whom we could get some clarity on the current state of the cache solutions on WMF cluster, and figure out how to get [[phab:T128486]] unstuck. **iOS ***release wikidiff2 to get section titles from compare endpoint ***counts endpoint limit increases ***minor count endpoint failing ( https://en.wikipedia.org/w/rest.php/v1/page/Barack_Obama/history/counts/min… ) * Updates: ** REST API extension interface documentation [[API:REST_API/Extensions]] === Engineering Productivity === ==== Release Engineering ==== * Blocking: ** SRE: Requesting follow-up from Releng team [[gerrit:479139]] * Updates: ** Train Health *** Last week: no train because of Wikimedia Technical Conference *** This week: no train because of team offsite *** Next week: 1.35.0-wmf.8 [[phab:T233856]] === Scoring Platform === * Blocking: ** SRE: Requesting follow-up from Scoring team [[phab:T233448#5638765]] * Updates: ** Team back from offsite in Austin ** We got a laptop to Uganda via DHL in a reasonable amount of time. === Search Platform === * Blocked by: ** Structured Data: Data dumps for SDC: [[phab:T221917]] * Blocking: ** WMDE/Wikidata: Not critically blocked by, but pinging the team to have a look at [[phab:T234431]]. * Updates: ** New elasticsearch servers configured and in production (elastic10[53-67].eqiad.wmnet) - [[phab:T230746]] ** Refactor Puppet WDQS module to make it usable for WDQS and CQS [[phab:T232297]] ** Metrics from the WDQS updater are no longer collected [[phab:T238408]] === Site Reliability Engineering === * Blocked by: ** Scoring Platform team: *** Requesting follow-up from Scoring team [[phab:T233448#5638765]] ** Releng: *** Requesting follow-up from Releng team [[gerrit:479139]] * Updates: ** [general update] Upcoming s1 (enwiki) database master switch 14 Nov: [[phab:T234800]] [will imply a small read only window] == Wikimedia DE == === Wikidata === * Blocked by: ** Search Platform: Not critically blocked by, but pinging the team to have a look at [[phab:T234431]]. ** Not sure who, Core Platform? Mentioned 2 times in SoS already with no result: In the Data Bridge work (editing Wikidata items from Wikipedia) we have encountered problems with Special:EntityData serving stale (old) data. The problem is quite old: [[phab:T128486]]. We are looking for a team/person with whom we could get some clarity on the current state of the cache solutions on WMF cluster, and figure out how to get [[phab:T128486]] unstuck. * Blocking: ** Structured Data: review of [[gerrit:548734]] ([[phab:T222497]])

2 1

2020 Community Wishlist Survey: Now Accepting Votes
by Ilana Fried 21 Nov '19

21 Nov '19

The 2020 Community Wishlist Survey is now accepting votes! This survey is the process where communities decide what the Community Tech team should work on over the next year. From now until 2 December, you can vote for which proposals you want us to address. We'll accept the top 5 wishes into our plans for next year.How to vote: Use the "Support" button at the top of each proposal. You can vote for as many proposals as you like. You're also allowed to canvas and encourage other editors to vote for a particular proposal.If you have questions about the survey, you can check out the survey page. Thank you, and we look forward to seeing your votes!Links: • Survey Page: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020 • Voting Rules: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020#voting • Proposals (click on a proposal to cast your vote): https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Tracking

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