Le 07/10/13 23:33, Krinkle a écrit :
Last Friday, the mw.Title rewrite landed in master. Here's a brief summary of
the changes.
For those willing to test it out in an environment similar to the
production wikis, you can use the beta cluster:
http://en.wikipedia.beta.wmflabs.org/
You should
Le 08/10/13 07:23, Matthew Flaschen a écrit :
There are really two parts of the status class:
* Setting error codes of varying severity (e.g. newGood for success,
newFatal for fatal error, error for a regular error), then letting the
caller check for them (e.g. hasMessage(), isOK and
On Tue, Oct 8, 2013 at 12:15 AM, Tim Starling tstarl...@wikimedia.org wrote:
On 08/10/13 14:40, Erik Bernhardson wrote:
A reviewer should be able to
know if the error conditions are properly handled by looking at the new
code, not by looking up all the function calls to see what they can
Hello,
Daniel Zahn and I will be rebooting gallium which is the Jenkins master.
The reboot is scheduled on Oct 10th at 8am and we last for a couple
hours while the server is busy fscking the huge disks.
Jobs will not be processed while the server is busy, I will retrigger
them manually.
Sorry
FYI
-- Forwarded message --
From: Core operations via RT core-...@rt.wikimedia.org
Date: Tue, Oct 8, 2013 at 12:14 PM
Subject: [wikimedia #5912] Upgrade PHP throughout the cluster to
5.3.10-1ubuntu3.8+wmf1 on Thursday 2013-10-08
To: akosia...@wikimedia.org
Scheduling an upgrade
Can we add an example of that usage to the status object with a note
not to follow the return this in case of error pattern that you
might see elsewhere in the code? It might even be worth a bit of
refactoring to get rid of the old pattern or people will still keep
finding it and copying it.
Hi everyone,
I'm excited to announce that Ori Livneh will be moving into Platform
Engineering as Senior Performance Engineer. This work is riffing off
of the work that he's done with the Growth (nee E3) team, where a big
part of his job was instrumenting new features to measure their impact
on
On 8 October 2013 11:59, Rob Lanphier ro...@wikimedia.org wrote:
Hi everyone,
I'm excited to announce that Ori Livneh will be moving into Platform
Engineering as Senior Performance Engineer.
Congratulations, Ori; great news, and I look forward to continuing to work
with you in your new
(Tangenially related: I made a proposal to eradicate Tidy some days ago over at
https://bugzilla.wikimedia.org/show_bug.cgi?id=54617 . I didn't look into
alternatives much yet – not enough free time – but
http://www.bioinformatics.org/phplabware/internal_utilities/htmLawed/index.php
looks
Hello everyone,
This summer, I was working on the project ZIM incremental updates for
Kiwixhttps://www.mediawiki.org/wiki/User:Kiran_mathew_1993/ZIM_incremental_updates_for_Kiwix
as part of GSoC 2013, under my mentors Emmanuel Engelhart and Tommi
Mäkitalo
The tools zimdiff and zimpatch-
Hi everyone,
Registration for the MediaWiki Architecture Summit is now open, and
will close Tuesday, October 22, 17:00 UTC (10am PDT). Here is the
essential event information:
January 23-24, 2014
SPUR - 654 Mission Street
San Francisco, CA, USA
Please put your name/information on the following
James Forrester wrote:
On 8 October 2013 11:59, Rob Lanphier ro...@wikimedia.org wrote:
I'm excited to announce that Ori Livneh will be moving into Platform
Engineering as Senior Performance Engineer.
Congratulations, Ori; great news, and I look forward to continuing to
work
with you in your
Hello,
So recently I've been trying to find a method where I could test database
queries on production data. I originally thought Tool Labs might help, but
I found out due to a bug in MySQL you can't perform EXPLAIN queries in the
database replicas. And naturally I don't have access to the actual
On 09/10/13 13:38, Tyler Romeo wrote:
Hello,
So recently I've been trying to find a method where I could test database
queries on production data. I originally thought Tool Labs might help, but
I found out due to a bug in MySQL you can't perform EXPLAIN queries in the
database replicas. And
On 10/08/2013 02:59 PM, Rob Lanphier wrote:
Hi everyone,
I'm excited to announce that Ori Livneh will be moving into Platform
Engineering as Senior Performance Engineer. This work is riffing off
of the work that he's done with the Growth (nee E3) team, where a big
part of his job was
15 matches
Mail list logo
