On Fri, Jun 12, 2015 at 5:33 PM, Lars Aronsson l...@aronsson.se wrote:
This is a suggestion to change search, so it ignores
postfix accents.
Russian dictionaries (including Wiktionary) use accents to
indicate stress on syllables, but these accents are never
seen in plain text.
In Russian
On Tue, Jun 9, 2015 at 2:19 AM, Gergo Tisza gti...@wikimedia.org wrote:
On Mon, Jun 8, 2015 at 4:16 PM, Brian Wolff bawo...@gmail.com wrote:
Additionally, from the help page, its not entirely clear about some of
the limitations. e.g. You can't do incategory:Foo OR intitle:bar.
regexes on
On Mon, Jun 8, 2015 at 7:16 PM, Brian Wolff bawo...@gmail.com wrote:
You can't do incategory:Foo OR intitle:bar.
regexes on intitle don't seem to work over the whole title, only word
level tokens (I think, maybe? I'm a bit unclear on how the regex
operator works).
intitle is word level
Some comments inline!
On Thu, May 21, 2015 at 4:43 AM, Quim Gil q...@wikimedia.org wrote:
Hi, thank you for this short and fresh review. Your help is welcome at
https://phabricator.wikimedia.org/T597, where we are trying to identify
blockers for using Arcanist, so we can discuss them and
On Mon, May 18, 2015 at 8:50 PM, MZMcBride z...@mzmcbride.com wrote:
Jonathan Morgan wrote:
On Mon, May 18, 2015 at 5:08 PM, Bahodir Mansurov
bmansu...@wikimedia.org wrote:
I doubt all 200 students will be making concurrent searches.
I can easily imagine a scenario where 200 students in a
On Mon, May 18, 2015 at 9:30 PM, John phoenixoverr...@gmail.com wrote:
If the stressor point is a few hundred hits, lets pick a value low enough
not to risk reaching the max, but high enough to not risk excessive
collateral damage, Something along the lines of 40-50 would avoid most
On Tue, May 5, 2015 at 4:28 PM, Bryan Davis bd...@wikimedia.org wrote:
Facebook uses a bot to transfer pull requests from GitHub [5] to their
Phabricator instance [6] for HHVM.
I gotta say I wasn't thrilled with it. It just felt all disjointed a
broken. As much as I like the idea of lowering
I've just tried it and it seems to be working well! I heard that some OSX
users were seeing huge huge performance problems with vagrant. Something
about having to run it inside a vm. I imagine running lxc inside a vm is
much less painful than running virtualbox
On Tue, Mar 3, 2015 at 3:24
tl/dr: The technology we started building against (Titan) is probably
dead. We're reopening the investigation for a backing technology.
Yesterday DataStax http://www.datastax.com/ announced
http://www.datastax.com/2015/02/datastax-acquires-aurelius-the-experts-behind-titandb
that they'd acquired
Top posting to add context: this is for the initiative to get a version of
Magnus' wonderful http://wdq.wmflabs.org/ running in production at WMF.
On Wed, Feb 4, 2015 at 4:50 PM, Nikolas Everett never...@wikimedia.org
wrote:
tl/dr: The technology we started building against (Titan) is probably
On Wed, Feb 4, 2015 at 5:09 AM, Yuri Astrakhan yastrak...@wikimedia.org
wrote:
flame war ahead
For those not adicted to slashdot, see here
http://news.slashdot.org/story/15/02/04/0332238/microsoft-open-sources-coreclr-the-net-execution-engine
.
Licenced under MIT
+1 for something like this. Its not a huge problem not to do semver but
it'd be simpler to explain if we did.
On Sun, Jan 25, 2015 at 10:27 AM, Legoktm legoktm.wikipe...@gmail.com
wrote:
On 01/15/2015 08:26 PM, Chad wrote:
I've been saying for over a year now we should just drop the 1. from
On Sat, Jan 3, 2015 at 11:30 PM, MZMcBride z...@mzmcbride.com wrote:
Jon Robson wrote:
Thoughts?
Adding easter eggs sounds like a fairly strange recruitment tactic, but I
don't see any harm in trying it out and seeing what happens. It's not
totally clear to me what problem we're trying to
On Nov 29, 2014 1:58 PM, Legoktm legoktm.wikipe...@gmail.com wrote:
On the talk page I suggested dropping the G prefix for top-level
repos, and just giving them an unprefixed callsign. I think that would
fix the ugliness of some of the frequently used names.
On Sat, 29 Nov 2014 17:51:11
I think that is a bit sad. Not tearing of cloths or gnashing of teeth sad.
Maybe stare whistfully into the sunset and think of what could have been
bad.
I'd prefer not to have them but I ultimately don't care that much. It does
provide a fun bikeshedding opportunity I guess.
Nik
On Nov 26, 2014
On Thu, Nov 13, 2014 at 4:14 PM, Brian Wolff bawo...@gmail.com wrote:
On 11/13/14, Chad innocentkil...@gmail.com wrote:
Please help me draft some guidelines for Phabricator repo callsigns.
https://www.mediawiki.org/wiki/Phabricator/Callsign_naming_conventions
The subpage on naming our
On Thu, Oct 30, 2014 at 10:18 PM, MZMcBride z...@mzmcbride.com wrote:
James Forrester wrote:
On 30 October 2014 09:53, Chad innocentkil...@gmail.com wrote:
New hardware is in place and we've got plenty of breathing room to wrap
up the migration to the new search engine.
Excellent news!
I can't access those links!
On Tue, Sep 16, 2014 at 11:14 AM, Daniel Kinzler
daniel.kinz...@wikimedia.de wrote:
Hi all!
The Wikibase team would like to allow data from any item to be used on any
client page. To do this, we need to track which item is being used where,
so we
can purge the
Also option 5 could be to continue without the days until the parser cash
is invalidated on its own.
Maybe option 6 could be to continue without the data and invalidate the
cache and completely rerender only some of the time. Like 5% of the time
for the first couple hours then 25% of the time for
On Tue, Sep 9, 2014 at 8:00 AM, Daniel Kinzler dan...@brightbyte.de wrote:
Am 09.09.2014 13:45, schrieb Nikolas Everett:
All those options are less good then just updating the cache I think.
Indeed. And that *sounds* simple enough. The issue is that we have to be
sure to
update the correct
If you've just started having vagrant issues, particularly if `vagrant
provision` has started complaining about git and vector then make sure to
pull the newest version of mediawiki.
Nik
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
Cirrus's dependencies are too get the integration tests passing and they
verify some stuff that came up in dictionary which doesn't force capitals.
I'm all for splitting the roles into basic ones and bloated ones.
On Aug 9, 2014 3:47 PM, Chad innocentkil...@gmail.com wrote:
On Sat, Aug 9, 2014
I'll have a look at it.
On Wed, Jul 2, 2014 at 12:29 PM, Florian Schmidt
florian.schmidt.wel...@t-online.de wrote:
Hello!
Is working for me. I have only opened your link in Google chrome and
searched for Android (search suggestions working, too) and click ok.
After this I see the result
try not to taunt it unless it is
seriously broken. Failing on all searches certainly counts so if it does
it again then please reply.
The BetaFeature search log is only complaining about errors that I know
about and am fixing, literally right now.
Nik
On Wed, Jul 2, 2014 at 12:34 PM, Nikolas
On Jun 18, 2014 2:28 PM, Brian Wolff bawo...@gmail.com wrote:
On 6/18/14, Kristian Kankainen krist...@eki.ee wrote:
Hello!
I think, if one is clever enough, some categorization could be automated
allready.
Searching for pictures based on meta-data is called Concept Based Image
Man! I'd love to go ride in a balloon and give a talk but Auckland is so
close to half way around the world
On Mon, Jun 16, 2014 at 11:36 AM, Sumana Harihareswara
suma...@wikimedia.org wrote:
Thanks, Luis! And for Tyler or anyone else on this list who has the same
questions:
Sometimes
I _thought_ someone was working on getting it to just work. For now,
though, if you start with a clean machine you can run the commands here:
https://www.mediawiki.org/wiki/Manual:PHP_unit_testing/Installing_PHPUnit#Using_PEAR
to get it installed. Make sure the use the pear commands because
On Fri, May 9, 2014 at 8:32 AM, J jollylittlebottom
jollylittlebot...@hotmail.com wrote:
If I search on http://www.mediawiki.org for Search Weighting I get as
result a line:
Search (section Search Weighting Ideas) with links to the page and to
the section.
This section contains the word
On Thu, Apr 10, 2014 at 3:43 AM, Faidon Liambotis fai...@wikimedia.orgwrote:
On Thu, Apr 10, 2014 at 05:04:38AM +0400, Max Semenik wrote:
And finally, appreciation: this was made possible only thanks to awesome
help from our search team, Nik Everett and Chad Horohoe. You kick ass
guys!
Now that TitleValue has been merged - what's next? I'll admit I'm an odd
choice to be sending out this email [1], but someone's got to do it. So,
I'm thinking, maybe:
1. Start on the TODO in Linker.php [2], turning it into a deprecated
compatibility interface calling HtmlPageLinkRenderer.
2.
On Fri, Mar 28, 2014 at 4:57 PM, Greg Grossmeier g...@wikimedia.org wrote:
== Wednesday ==
* Cirrus Search will be graduated from Beta Feature to enabled for all
users on all non-wikipedia wikis (eg Commons, etc)
** https://www.mediawiki.org/wiki/Search
I'd prefer to do commons on its
Are either one of you opted into the New Search BetaFeature?
Nik
On Mon, Mar 17, 2014 at 9:01 AM, John phoenixoverr...@gmail.com wrote:
It works for me.
On Monday, March 17, 2014, David Cuenca dacu...@gmail.com wrote:
Hi,
When I type bach on the top right en.wp search box, I only
opting out, it works fine.
Thanks for the hint!
Micru
On Mon, Mar 17, 2014 at 2:16 PM, Nikolas Everett never...@wikimedia.org
wrote:
Are either one of you opted into the New Search BetaFeature?
Nik
On Mon, Mar 17, 2014 at 9:01 AM, John phoenixoverr...@gmail.com wrote
Looks like I lied: I'll have to make a software change to fix this after
all It'll be more then a few hours but I'll reply on the bug when it
is really fixed.
On Mon, Mar 17, 2014 at 9:44 AM, Nikolas Everett never...@wikimedia.orgwrote:
Filed: https://bugzilla.wikimedia.org/show_bug.cgi
CirrusSearch flaked out Feb 28 around 19:30 UTC and I brought it back from
the dead around 21:25 UTC. During the time it was flaking out searches
that used it (mediawiki.org, wikidata.org, ca.wikipedia.org, and everything
in Italian) took a long, long time or failed immediately with a message
I can make a better case for hiding things from internal search then I did
on the bug. I'll send it here and copy it to the mailing list:
The biggest case I can think of for excluding text from search is the
license information on commons. Please take that as an example. Maybe it
is the only
On Wed, Feb 19, 2014 at 12:17 PM, Helder . helder.w...@gmail.com wrote:
On Wed, Feb 19, 2014 at 12:14 PM, Nikolas Everett
never...@wikimedia.org wrote:
The big problem with the nosearch class implementation is that it'd be
pretty simple to abuse and hard to catch the abuse because the text
On Fri, Jan 24, 2014 at 8:55 PM, Daniel Kinzler dan...@brightbyte.dewrote:
Am 24.01.2014 14:44, schrieb Brad Jorsch (Anomie):
It looks to me like the existing patch *already is* getting too far into
the Javaification, with it's proliferation of classes with single methods
that need to be
I hate to say this after all you went through setting up Lucene Search but
it is end of life and not receiving any real support. We're in the process
of replacing it with the combination of
CirrusSearchhttps://www.mediawiki.org/wiki/Extension:CirrusSearch
/Elasticsearch
I like the idea. I wonder a few things:
1. Is this something that only makes sense to do for the help namespace?
2. Would it be good enough to catch help me kinds of queries and provide
a did you mean-like suggestion for a new search that'd actually search
help?
Nik
On Mon, Jan 6, 2014 at
On Fri, Dec 27, 2013 at 1:30 PM, Chad innocentkil...@gmail.com wrote:
On Fri, Dec 27, 2013 at 12:34 PM, Jon Robson jdlrob...@gmail.com wrote:
I want a templating system that can be used both in PHP and JavaScript
and
fits in our way of doing i18n. And a bunny.
I'm not sure if
I wonder if this is 38273 revived. Like 58042 was. Cirrus hasn't changed
this code so I'm reasonably confident it isn't us this time. Though it is
still possible given that we're on mediawikiwiki and itwiki.
On Wed, Dec 18, 2013 at 4:23 AM, Federico Leva (Nemo) nemow...@gmail.comwrote:
Did
SpecialSearchResultsPrepend lets you add html directly to the search page
but doesn't let you add your own results. The html actually gets injected
above the search for so it'd take some css trickery to move it. Example:
This wiki is using a new search engine. (Learn
in the documentation. I
implemented the later to add a section below the standard search results
that lists results from my system. Seems to be working for now and
requires no patching of the core code.
P
On Fri, Dec 13, 2013 at 8:55 AM, Nikolas Everett never...@wikimedia.org
wrote
Note that the wikis that say they were deployed on December 11th but do not
have a strike through them have Cirrus running, but their indexes are still
being built. I believe OAuth will be broken on those wikis as well.
This requires two fixes to actually fix, both of which are in review state
On Thu, Dec 12, 2013 at 11:53 AM, Nikolas Everett never...@wikimedia.orgwrote:
Note that the wikis that say they were deployed on December 11th but do
not have a strike through them have Cirrus running, but their indexes are
still being built. I believe OAuth will be broken on those wikis
Normally:
* clone a repo
* setup git hooks
# patch 1:
* git checkout -b some_branch_name
* apply my changes
* git commit -a
* git review
# patch 2:
* git checkout production (or master on non-puppet repositories)
* git pull
* git checkout -b some_other_branch_name
* apply my changes
* git
On Wed, Nov 20, 2013 at 9:01 AM, Petr Bena benap...@gmail.com wrote:
when I did a new branch before git-review it now show this as topic
in gerrit: https://gerrit.wikimedia.org/r/#/c/96484/
will it merge this to production branch?
Yes.
___
Package Control is you friend. How else do you install a linter or syntax
highlighting for a new language without touching a mouse?
On Tue, Nov 19, 2013 at 2:42 PM, Tomasz Finc tf...@wikimedia.org wrote:
On Tue, Nov 19, 2013 at 3:35 AM, Krinkle krinklem...@gmail.com wrote:
DocBlockr
Nice.
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
On Mon, Oct 7, 2013 at 3:12 PM, Jeroen De Dauw jeroended...@gmail.com wrote:
Hey,
We use lots of libraries that happen to use composer. We just don't
use composer to deploy them.
Oh? Lots? Is there a list somewhere? Are most of those libraries forked?
Are a good portion of them
On Mon, Oct 7, 2013 at 3:45 PM, Brion Vibber bvib...@wikimedia.org wrote:
I've heard the vague claim that exceptions are confusing for years, but for
the life of me I've never seen exception-handling code that looked more
complex or confusing than code riddled with checks for magic return
On Tue, Sep 24, 2013 at 12:00 PM, David Gerard dger...@gmail.com wrote:
I just went looking for the word referer. The response started with
lots of instances of the word reference. Put it in quotes, no
difference. Eventually resorted to Google.
Is MW.org using the exciting new search engine?
On Mon, Sep 23, 2013 at 12:40 PM, Chris McMahon cmcma...@wikimedia.org wrote:
So nice to see what Nik has done here. Information on running these tests
is in the README:
On Sat, Sep 21, 2013 at 10:26 AM, Chad innocentkil...@gmail.com wrote:
On Fri, Sep 20, 2013 at 11:47 PM, billinghurst billinghu...@gmail.comwrote:
Excellent news! Would someone be able to provide or point to some
configuration and examples that English Wikisource can utilise to allow
some
On Thu, Sep 19, 2013 at 4:04 PM, Dan Andreescu dandree...@wikimedia.org wrote:
- Has http://learnboost.github.io/stylus/ been considered? I've heard that
it's a good compromise between sass and less (but I haven't played with it
myself to see if it really lets you do more compass-like things).
On Sat, Sep 7, 2013 at 5:29 PM, MZMcBride z...@mzmcbride.com wrote:
Federico Leva (Nemo) wrote:
Nice! As for next steps, what about using Wiktionary as next pioneering
project for the new CirrusSearch (first opt-in and then default)?
It exists in most languages (we really need to see how the new
I worked on an accounting system with similar requirements and we had
an even more complicated system but one you might want to consider:
1. When something happens record the event and how much it changed
the value along with a timestamp. In our case we'd just have enable
and disable events.
2.
Today we threw the big lever and turned on our new search backend at
mediawiki.org. It isn't the default yet but it is just about ready for you
to try. Here is what is we think we've improved:
1. Templates are now expanded during search so:
1a. You can search for text included in templates
1b.
On Wed, Aug 28, 2013 at 3:37 PM, Paul Selitskas p.selits...@gmail.comwrote:
Will it be set as the search backend further on Wikimedia projects?
Yes. I'm not sure when though.
Is there source code available for Elasticsearch on Gerrit?
Our plugin that interacts with Elasticsearch is
On Tue, Aug 27, 2013 at 2:48 PM, Tyler Romeo tylerro...@gmail.com wrote:
I know this list isn't really for linking stuff, but I found this article
earlier today:
http://zenol.fr/site/2013/08/27/an-alternative-error-handling-strategy-for-cpp/
It's about C++, but what it describes is very
On Thu, Aug 15, 2013 at 8:09 PM, Daniel Friesen
dan...@nadir-seen-fire.comwrote:
Wait, Elasticsearch? I thought the original discussions were about Solr?
It certainly started that way but there were but some rather insistent
folks talked me in to giving Elasticsearch a chance. I spent a week
Scott,
I was going to respond to this a while ago but couldn't really do it
justice. I'm still pretty sure my explanation won't be great, which is an
indication of just how good Google is.
For strait search there is nothing we can do that Google can't. It might
cost them more time and money to
://www.mediawiki.org/w/index.php?title=Requests_for_comment%2FCirrusSearchdiff=740790oldid=728213
Nik Everett
On Fri, Jun 14, 2013 at 4:21 PM, Nikolas Everett never...@wikimedia.orgwrote:
So Chad and I feel like we've gotten far enough in our prototype of our
new search backend for MediaWiki that we're
As a ChromeOS user I really just think of it as a laptop with a funky set
of apps. I'm pretty sure I wouldn't have thought to search for a wikipedia
app for it because I'm so used to getting wikipedia in the browser.
On the other hand if the app could modify search key behaviour so I can hit
I'm not sure about http://www.mediawiki.org/wiki/Help:Searching but
https://en.wikipedia.org/wiki/Help:Searching has lots of things we're going
to have to add to our list. My guess is
http://www.mediawiki.org/wiki/Help:Searching is simply out of date.
Nik
On Mon, Jun 17, 2013 at 4:33 PM, Chris
wrote:
Just as a note, MediaWiki default (aka crappy) search is very
different from the lucene stuff used by Wikimedia. Lucene search is
rather difficult to set up, so most third party wikis do not use it.
--bawolff
On 6/17/13, Nikolas Everett never...@wikimedia.org wrote:
I'm not sure
So Chad and I feel like we've gotten far enough in our prototype of our new
search backend for MediaWiki that we're ready to request comments. So here
is our format RFC:
https://www.mediawiki.org/wiki/Requests_for_comment/CirrusSearch
You'll note that the plugin is called CirrusSearch.
On Tue, Jun 4, 2013 at 12:36 PM, Jeroen De Dauw jeroended...@gmail.comwrote:
Hey,
My own experience is that test coverage is a poor evaluation metric
for anything but test coverage; it doesn't produce better code, and
tends to produce code that is considerably harder to understand
I have no qualms with any of the guidelines. They are good guidelines but
like all guidelines they are made to be bent when appropriate so long as
you leave a good explanatory comment. My main concern is that the article
is about test how to write more unit testable code which is something I
On Mon, Jun 3, 2013 at 10:20 AM, Jeroen De Dauw jeroended...@gmail.comwrote:
4. Don't write automated tests at all and do lots of code reviews and
manual testing. Sometimes this is really the most sensible thing. I'll
leave it to you to figure out when that is though.
Absolutist
71 matches
Mail list logo
