Wikitech-l December 2014

wikitech-l@lists.wikimedia.org

88 participants
95 discussions

eliminate wgParser from WikitextContent
by Keith Welter 18 Dec '14

18 Dec '14

Can anyone think of a reason *not* to eliminate wgParser usage from WikitextContent? I have a bug (T76651) that is resolved by making WikitextContent use its own parser instance rather than wgParser. I wrote an experimental fix of WikitextContent that clones the parser in the same way as MessageCache::getParser and am trying to decide the best way forward. Thanks, Keith Welter

2 1

Scrum of Scrums Notes for 2014-12-17
by Dan Andreescu 17 Dec '14

17 Dec '14

https://www.mediawiki.org/wiki/Scrum_of_scrums/2014-12-17

1 0

Welcome, Marko Obrovac, to the Services team
by Rob Lanphier 17 Dec '14

17 Dec '14

Hi everyone I'm pleased to (belatedly) welcome another new member of the Services team: Marko Obrovac. Marko started working in the Services team with Gabriel Wicke and James Douglas on RESTbase. Marko comes to us from Reflected Networks, a Croatian web-hosting company specializing in high-traffic websites. While there he developed a distributed message passing framework for their monitoring system there. Prior to that, Marko earned his PhD at Université de Rennes I / IRISA, INRIA, focused on distributed systems, such as AutoChem (a chemical computuing system) and XtreemOS (grid operating system) and kDFS (a symmetrical distributed file system) Marko is in the process of relocating to Marseille, France, where he'll be in January. You can find Marko on Freenode IRC as "mobrovac". Welcome, Marko! Rob

2 1

MediaWiki flame graphs
by Ori Livneh 16 Dec '14

16 Dec '14

I'm writing to draw your attention to a newly-available resource for performance analysis: flame graphs of MediaWiki code. http://performance.wikimedia.org/xenon/svgs/ Flame graphs are a visualization of application stack traces. Each application server on the Wikimedia cluster has a software timer that interrupts MediaWiki once every ten minutes to capture a stack trace. The stack trace shows what the code the application server was in the process of executing when the timer expired. A central log aggregator collects these traces and uses them to generate flame graphs. Each box in a flame graph represents a function in the stack. The y-axis shows stack depth. The topmost box shows the function that was on-CPU at the moment the trace was captured. The function below a function is its parent. The x-axis spans the sample population. The width of the box shows the total time it was on-CPU or part of an ancestry that was on-CPU, based on sample count. Here is an example: http://performance.wikimedia.org/xenon/svgs/hourly/2014-12-15_22.svgz To learn more about flame graphs and how to interpret them, see < http://www.brendangregg.com/flamegraphs.html>.

2 1

Live preview
by Derk-Jan Hartman 16 Dec '14

16 Dec '14

Hi all, I've had a significant update to Live Preview in the pipeline for a while now. It brings a few major improvements, the most important of it being able to load resourceloader modules that the preview requires, fixing a whole slew of problems that the old implementation had. The only place where it is a bit limited is with regard for previewing the list of languages in in skins other than vector. The code is here: https://gerrit.wikimedia.org/r/#/c/131346/ <https://gerrit.wikimedia.org/r/#/c/131346/> And it could use some user testing and review. Some people have been asking me about this lately, so I figured time to strip the WIP tag of it and see if we can get this merged already. Long term, I would like to improve it to make use of mw.template for some of the elements, but that is not a necessity right now I think. DJ

3 2

RFC meeting this week
by Tim Starling 16 Dec '14

16 Dec '14

In the next RFC meeting we would like to discuss the following RFC: * Release notes automation <https://www.mediawiki.org/wiki/Requests_for_comment/Release_notes_automation> The meeting will be on the IRC channel #wikimedia-office on irc.freenode.org at the following time: * UTC: Wednesday 21:00 * US PST: Wednesday 13:00 * Europe CET: Wednesday 22:00 * Australia AEDT: Thursday 08:00 -- Tim Starling

1 0

Re: [Wikitech-l] [Engineering] MediaWiki flame graphs
by Jon Robson 16 Dec '14

16 Dec '14

These are pretty cool. I'd love to see a mobile specific one: https://phabricator.wikimedia.org/T78621 On Mon, Dec 15, 2014 at 3:48 PM, Aaron Schulz <aschulz(a)wikimedia.org> wrote: > Cool! > > On Mon, Dec 15, 2014 at 3:42 PM, Ori Livneh <ori(a)wikimedia.org> wrote: >> >> I'm writing to draw your attention to a newly-available resource for >> performance analysis: flame graphs of MediaWiki code. >> >> http://performance.wikimedia.org/xenon/svgs/ >> >> Flame graphs are a visualization of application stack traces. >> >> Each application server on the Wikimedia cluster has a software timer that >> interrupts MediaWiki once every ten minutes to capture a stack trace. The >> stack trace shows what the code the application server was in the process of >> executing when the timer expired. A central log aggregator collects these >> traces and uses them to generate flame graphs. >> >> Each box in a flame graph represents a function in the stack. The y-axis >> shows stack depth. The topmost box shows the function that was on-CPU at the >> moment the trace was captured. The function below a function is its parent. >> >> The x-axis spans the sample population. The width of the box shows the >> total time it was on-CPU or part of an ancestry that was on-CPU, based on >> sample count. >> >> Here is an example: >> http://performance.wikimedia.org/xenon/svgs/hourly/2014-12-15_22.svgz >> >> To learn more about flame graphs and how to interpret them, see >> <http://www.brendangregg.com/flamegraphs.html>. >> >> >> _______________________________________________ >> Engineering mailing list >> Engineering(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/engineering >> > > > -- > -Aaron S > > _______________________________________________ > Engineering mailing list > Engineering(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/engineering >

1 0

Design/Event for your Project or Event?
by Rachel Farrand 15 Dec '14

15 Dec '14

Hello! I am a mentor for Google Code In this year and am looking for ways to help the engineering community and engage the students in the program. If you have a project, event or team that that needs a logo, t-shirt design, sticker design, etc. Please let me know and I will be happy to help get your project into GCI and mentor it for you. I cannot promise you professional level results, but you might be pleasantly surprised with what comes back. You may end up with something you want to use that way it is or you may end up with some inspiration. No harm in trying anyways and it is a great opportunity for the students to become introduced and exposed to corners of the wikimedia communities that they might not otherwise find. If you would like to work together on this, please email me back and let me know what you are looking for/thinking of and an guidelines you have. More information about Google Code In here: https://developers.google.com/open-source/gci/ Thanks! Rachel

1 0

Check your MediaWiki extensions tests against hhvm
by Antoine Musso 15 Dec '14

15 Dec '14

Hello, I have added Jenkins jobs to run your extension PHPUnit tests with hhvm. Since the tests might be failing, the job is not triggered on patchset proposal, one has to comment in Gerrit 'check experimental'. Please do so on your favourite extensions or patches and report back any issue there :] I will make the job to trigger on patch proposal by the end of the week. Note: I have already added an HHVM based job for mediawiki-core. It is non voting for now pending upgrade of our hhvm version. cheers, -- Antoine "hashar" Musso

1 0

Your oldest Phabricator tasks
by Quim Gil 15 Dec '14

15 Dec '14

Somehow I got into the habit of checking this Phabricator report linking to the oldest open task assigned to each user: https://phabricator.wikimedia.org/maniphest/report/?order=-oldest-all Your username probably appears in this list. If not, it's probably time to take a task and assign it to you. :) There are 223 users with tasks assigned, from which 132 have a task assigned that was created at least one year ago. At least in the upper section of the list, most tasks welcome a fresh look, and your help is welcome (starting by your own tasks). There is a convenient tooltip showing the title of the tasks linked. There is a complementary view of the same list, sorting users by number of tasks assigned. https://phabricator.wikimedia.org/maniphest/report/?order=-total I'm currently 20th with 24 tasks assigned, which is already unrealistic. You might want to re-check your assigned tasks for everybody's benefit and your own. See also https://www.mediawiki.org/wiki/Phabricator/Project_management#Assigning_tas… -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

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 December 2014