similar to: trac browser "Access Denied"

Hi Folks, I''ve just released version 0.9.0. This latest version of Ferret is an alpha release. I have removed the old c extension and Ferret is now running on a fully ported C library. This has allowed some huge performance improvements both with regard to memory and CPU usage. There will probably be a few portability issues to start with. It has been developed on Linux so it should

Hi, I posted a Trac ticket about it, but I thought I''d ask the mailing list to reach more people. I''m using these filters together in my analyzer (with acts_as_ferret + Ferret 0.11.1). HyphenFilter.new( StopFilter.new( LowerCaseFilter.new( MappingFilter.new(

Hey guys, I''ve been trying out ferret 0.9.3 on my powerbook this weekend and I''ve been triggering ''bus errors'' when using the Query API. If I programmatically build up strings, it works just fine. There''s some more information available in the trac ticket http://ferret.davebalmain.com/trac/ticket/62 Is anyone successfully using the Query API on

Hi folks, This latest release of Ferret has a lot of improvements. There have been substantial improvements to performance. Try it for yourself to see. I won''t be publishing any numbers just yet. I will say though that it''s still about 2-4 times slower than Lucene with the extension installed. There is also some performance improvements in the pure Ruby version if you

Folks, Since upgrading to ferret 0.11.4 on Mac OS X Tiger, I''ve been running into constant crashes when running my Rails tests. Here''s an example of the output. -- snip -- 1) Error: test_published_blog_can_be_ferreted(BlogTest): Ferret::FileNotFoundError: File Not Found Error occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input

Hi guys, Having committed a fairly large project to ferret I''m a little concerned that ferret svn has been essentially unavailable for weeks (pretty much every time I try I get "can''t connect") and more so now that davebalmain.com has gone off the air. Without meaning to pry, does anyone know whether existing problems in ferret are likely to get fixed? (I can get

Hey all, just recently I stumbled upon this http://ferret.davebalmain.com/trac/timeline which seemed like good news. I thought Ferret was put on hold or perhaps dying, and having participated recently in a few discussions with people who also thought that was the case, I didn''t have a good answer for it. So, is anyone informed if there will be some development going on Ferret, as in

I just posted a ticket regarding possible memory leaks in the c layer exception handling: http://ferret.davebalmain.com/trac/ticket/187 (This mail is just to draw attention to it :) regards, //Martin -- ################################################################### Things are more like they used to be than they are now. ###################################################################

Hi dave, and everyone ;) I''ve finished my extension to export Index.search(..) loaded results into json. Here''s a little benchmark of what i''ve done : >> Benchmark.realtime { INDEX.search(query, :limit => 1000).hits.each { |x| INDEX[x.doc].load.to_json } } => 7.38711595535278 >> Benchmark.realtime { INDEX.search(''type:hardware'',

Hey guys, It has occurred to me that a lot of people need some of the fixes I make to Ferret ASAP and don''t like having to wait to long for the gem. On the other hand, it is a bit of a pain to download and install from subversion because then you need to uninstall when the next gem comes out. So I thought I may as well put some instructions out as to how you can build your own Ferret gem

Hi ferreteers, I came across a segfault in the query parser. It had already been reported[1] and fixed[2], but it can lead to a denial of service. If you use Ferret anywhere that you allow users to execute queries, those users can crash your Ruby process with a specially crafted query. I''m sure you''re all using Monit or something for your Rails or drb processes, so

The ferret webpage at http://ferret.davebalmain.com/ has been down for a number of days. Any idea what''s going on? or how to notify the webmaster? -- Posted via http://www.ruby-forum.com/.

Remember folks, we can support the Ferret project by donating warm soft electronic cash to the author, Dave Balmain, using the paypal buttons on the website: http://ferret.davebalmain.com/trac http://ferret.davebalmain.com/trac/wiki/DonationsFAQ We can also buy the Ferret Shortcut pdf/book from O''Reilly, also written by Dave Balmain. It''s awesome good:

Hi folks, Just thought I better let you all know that I''m still working on the next release of Ferret. I''ve been working the last 7 days doing nothing but Ferret development. The last iteration generated a diff of almost 5000 lines so there are some pretty major changes. Most people won''t notice these changes however as the API remains unchanged. But if you were having

Hi, I just checked out ferret 0.10.14 from subversion and am getting intermittent failures from the thread_safety_index_test.rb script. Sometimes it runs through to the end with no errors, but other times I get errors, including segfaults. I reported the bug here: http://ferret.davebalmain.com/trac/ticket/153 Can anyone else reproduce this? svn co

I''m having trouble with PerFieldAnalyzer (ferret version 0.10.14). Script: require ''rubygems'' require ''ferret'' require ''pp'' include Ferret::Analysis include Ferret::Index class TestAnalyzer def token_stream field, input pp field pp input LetterTokenizer.new(input) end end pfa =

I had sort-by-date working almost perfectly with my app. It was behaving as expected for most data, but had a few hiccups with certain data. I investigated and discovered that the correct data was storing this in my ferret index: "1999-10-18 00:00:00" and the incorrect data was storing this: "Mon Oct 18 00:00:00 EDT 1999" (oops...) So I of course had to fix the

Hi Dave, I''ve been getting some segment faults while running my tests using 0.10.14 gem so I decided to package the gem locally to add -dH and generate core dumps for you. So I followed instructions here http://ferret.davebalmain.com/trac/wiki/DownloadCurrent and first off ran the tests. I''m getting the following failures. (see this pastie http://pastie.caboo.se/34790). I

I may have run across a bug in Ferret: if throws a segmentation fault when I try to create a Sort object using the default fields (SCORE and DOC_ID), but setting reverse to true. Here''s the minimal example: #!/usr/bin/env ruby require ''rubygems'' require ''ferret'' Ferret::Search::Sort.new Ferret::Search::Sort.new( [

I use ferret on a danish site where I would like ferret to search word like "under" and "and". These are words that are excluded by ferret but have a different meaning in danish. Can you dissable this in ferret? Cheers Mattias -- Posted via http://www.ruby-forum.com/.