Hey,
So I'm working on making an S3 file backend for E:AWS, but I've run into an
issue. FileBackend::doCreateInternal expects an array of options, one of
those options should be an array of headers, e.g., Content-Type. Amazon S3
needs the Content-Type header, otherwise it just shows up as a file
Re: ([01]+)
I was sorry about the Wikidata insanity, and am glad to see you around.
Templates are one way to go but I think using a real markup tag to mark
them up would be even better.
This would make the tag cheaper to process and would require making
a fairly trivial extension. Regarding
the
Forwarding a link from the EE list for the enjoyment of workaholics and
volunteers who check their email on weekends. If you get this email while
you're working paid time, please wait until you're on free time. (:
http://martinvalasek.com/blog/pictures-from-a-developers-life
Cheers,
Pine
Talkpages are being redesigned to use a more object-based setup, which
should make tagging things a lot easier, but this still holds - those
objects will be taggable, but also there are years worth of old
discussions on many projects that may still wind up benefiting from a
section-based
Le 03/03/13 09:39, ENWP Pine a écrit :
Forwarding a link from the EE list for the enjoyment of workaholics and
volunteers who check their email on weekends. If you get this email while
you're working paid time, please wait until you're on free time. (:
Le 01/03/13 09:47, Tim Starling a écrit :
On 01/03/13 05:22, Petr Bena wrote:
I believe it would require to create a new daemon (preferably written
in c++) which I am willing to write, that could do similar what the
ircd does right now. And that is delivery of new change to all
connected
On Sun, Mar 3, 2013 at 5:07 AM, Tyler Romeo tylerro...@gmail.com wrote:
Hey,
So I'm working on making an S3 file backend for E:AWS, but I've run into an
issue. FileBackend::doCreateInternal expects an array of options, one of
those options should be an array of headers, e.g., Content-Type.
Date: Sun, 03 Mar 2013 11:40:55 -0800
From: Antoine Musso hashar+...@free.fr
To: wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] Pictures from a developer's life
Message-ID: kh0900$qqd$1...@ger.gmane.org
Content-Type: text/plain; charset=UTF-8
Le 03/03/13 09:39, ENWP Pine a écrit
I was looking for a way to test my fix to
https://bugs.php.net/bug.php?id=64338 and, having spent so much time on
MediaWiki, I thought MW would provide a good way to test the connection
to a MS SQL database.
I was somewhat surprised to see that even though we have a
db/DatabaseMssql.php, we
On Sun, Mar 3, 2013 at 4:37 PM, Brion Vibber br...@pobox.com wrote:
For a File::upload() implementation I think you'll want to grab
$this-getMimeType() and send it as necessary.
The only problem is that at that point I don't have a File object to use.
When it gets to the FileBackend, it only
Because resources are expensive, we decided to make few huge instances
on bots project rather than ton of small as we have now.
So in upcoming weeks it would be cool to migrate all db's from sql1
sql2 and sql3 to bsql01 which has 16gb ram and 160gb storage
you might want to move your bots from
Have a look at
https://en.wiktionary.org/wiki/User:Yair_rand/addcomment.js
It allows you to add a comment, signed and correctly
indented, to the end of a section of a talk page.
It works fine on my Android phone, which is more than
can be said of the regular edit function.
The discussion
fwiw this is not a discussion about Gerrit features but about git commit
and code contribution good practices in general. There is plenty of
literature out there.
I also prefer it in the header. The bug report is the best description :)
A bug report is supposed to describe a problem while
On 2013-03-03 9:36 PM, Quim Gil q...@wikimedia.org wrote:
[...]
Plus quite frequently a bug is fixed through more than one commit, and
still you are supposed to explain in each commit message what you are doing
in that commit
I don't see that as being an issue. If anything its an argument for
On Sun, Mar 3, 2013 at 9:06 PM, Brian Wolff bawo...@gmail.com wrote:
The primary argument for changing the format is so gerrit can index it.
Beyond the /sounds like a gerrit problem/ argument presented previously, I
would additionally argue that that is not that useful a feature. (Even if
on
FWIW, I also prefer to have those 10 extra characters in the header. Also,
when I'm scanning the git shortlog, I don't give a damn about bug numbers,
because if I care enough about a commit to want to check its bug report,
it's very likely I'm already looking at the full commit message anyway.
MediaWiki Bugzilla Report for February 25, 2013 - March 04, 2013
Status changes this week
Bugs NEW : 458
Bugs ASSIGNED : 81
Bugs REOPENED : 50
Bugs RESOLVED
I don't know what others have done, but I have generally been able to just
add the MSSQL option to the installation scripts and install as for other
DBMSs and update the code to parallel the changes that have been made for
the MySQL driver. My updates typically don't get added into the git
Problem:
Extension:OpenID adds a new pref tab (OpenID) [1,3],
but the fieldset.../fieldset, and legendsection header texts/legend
are apparently _not_ correctly set up in the page HTML, or they are not
correctly rendered.
See [3].
Pls compare [3] (sections missing) and [4] (correctly
Le 03/03/13 14:21, Mark A. Hershberger a écrit :
I imagine this is because when the installer was re-written, no one was
around to implement it for MS SQL. Are SQL Server users just updating
their old MW installations?
Given the installer has been around for a few years, I guess we should
On Sun, Mar 3, 2013 at 10:02 PM, Antoine Musso hashar+...@free.fr wrote:
Le 03/03/13 14:21, Mark A. Hershberger a écrit :
I imagine this is because when the installer was re-written, no one was
around to implement it for MS SQL. Are SQL Server users just updating
their old MW installations?
what is missing in the code ?
If you want the fieldset to appear, I believe you just need to change
all the 'section' = 'openid', in the preference arrays to 'section'
= 'openid/openid', and then it will use the prefs-openid message,
which you have already defined, as the section text in the
On Sun, Mar 3, 2013 at 6:06 PM, Brian Wolff bawo...@gmail.com wrote:
Personally I prefer it in the first line. Second to a good one line summary
of what was done, the bug number is the next most important thing. It
allows one to see the context the commit was made in. Having it in the
first
Am 04.03.2013 07:47, schrieb Grunny:
what is missing in the code ?
If you want the fieldset to appear, I believe you just need to change
all the 'section' = 'openid', in the preference arrays to 'section'
= 'openid/openid', and then it will use the prefs-openid message,
which you have already
On 03/03/2013 01:49 PM, ENWP Pine wrote:
Date: Sun, 03 Mar 2013 11:40:55 -0800
From: Antoine Musso hashar+...@free.fr
To: wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] Pictures from a developer's life
Message-ID: kh0900$qqd$1...@ger.gmane.org
Content-Type: text/plain;
25 matches
Mail list logo
