similar to: Time and DateTime default precision :day not :second ?

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

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

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, I''ve adapted my ferret_killer1.rb script to reproduce the segfaults I''m still having in my app with Ferret 0.11.3. ferret_killer1 didn''t reproduce these - I had to add code to retrieve the documents from the index after searching (and fixed the index creation bug Dave spotted). http://johnleach.co.uk/downloads/ruby/ferret/ferret_killer3.rb To use, in one terminal

Hi, I noticed a 0.11.3 release and gave it a whirl. I''ve so far not been able to reproduce any segfaults with my ferret_killer[1] script, though I do get some errors. when the searching process is running and I start the indexing process, I immediately get: /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:692:in `latest?'': File Not Found Error occured at

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

Hey guys, I''ve just removed the -fno-stack-protector flag from the release so those who had trouble because of this should now be able to install 0.11.2-rc3. If you have any problems with this release, please let me ASAP. Cheers, Dave -- Dave Balmain http://www.davebalmain.com/

Is there a fast way to determine how many documents a term occurs in, besides iterating through every document with TermDocEnum? -- Best regards, Stian Gryt?yr

Hi, I''m using ferret and running into troubles with it seg faulting during searches. The index I''m searching is static and is only updated in an offline way once every couple weeks. The segfault isn''t deterministically reproducible, but if I hammer ferret hard enough I can reliably get it to crash. The problem seems to have something to do with how memory is shared

Hey folks, Sorry for cross posting like this but this is an important announcement for all Ferret users. ** Description ** Firstly for those who don''t know, Ferret is a full-text search library which makes adding search to your application a breeze. It''s much faster than MySQL full-text search as well most other search libraries out there. It allows you to do Boolean (+ruby +

Hello, Here''s the code that segfaults: http://pastie.caboo.se/36467 I could have submitted a patch, but I''m not sure whether this segfault is caused by Ferret or Ruby. This seems to be triggered only when combining a split and a gsub on an empty string of the returned array, and trying to insert it directly into the index. However, there''s no problem when you

According to the Analyzer doc and the StandardTokenizer doc: http://ferret.davebalmain.com/api/classes/Ferret/Analysis/Analyzer.html http://ferret.davebalmain.com/api/classes/Ferret/Analysis/StandardTokenizer.html I ought to be able to construct a StandardTokenizer like this: t = StandardTokenizer.new( true) # true to downcase tokens and then later: stream = token_stream(

Ferret throws a bus error in the unit tests under Solaris, sun4u architecture. http://ferret.davebalmain.com/trac/ticket/272 Bug reporter appears to be on Solaris 8 with Ruby 1.8.4. I''ve tried on Solaris 10 (first release and 10/06, first without and then with the most recent patch set), both with Ruby 1.8.6, and get exactly the same error in the same spot. Tried with 0.11.4 and also

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''m adding some news articles to a keyed Ferret 0.10.14 index and encountering quite serious instability when concurrently reading and writing to the index, even though with just 1 writer and 1 reader process. If I recreate the index without a key, concurrent reading and writing seem to work fine (and indexing is about 10 times quicker :) I''m testing by running my indexing

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

Hello all, I recently upgraded from the Ferret gem 0.11.4 to the Subversion trunk, changeset #770. I did this because I needed the large file patch from http://ferret.davebalmain.com/trac/ticket/215 When adding documents to the index, I get the following message printed to STDERR many times: Warning encoding error. Please check that you are using the correct locale for your input

Hi, I''m having some strange/random crashes with ferret when using different programs on the same index. I created a script to reproduce the errors: http://www.sig11.org/~seb/ferret_crash.rb Usage: In one terminal run: ruby ferret_crash.rb first In another terminal: ruby ferret_crash.rb Errors I usually get are but it is really random:

Is Ferret''s SVN repository down? I''m trying to get the source from svn://davebalmain.com/ferret, but I keep getting "Connection Refused" errors. Did the URL change, or is Ferret''s repository really down? -- Bira http://compexplicita.wordpress.com http://compexplicita.tumblr.com

Greetings, I''ve been using ferret with great results now for a while, but in the last week, I''ve been running into some issues. I will occasionally see this message: Exception Message: Lock Error occured at <except.c>:103 in xpop_context Error occured in index.c:5368 - iw_open Couldn''t obtain write lock when opening IndexWriter Which is accompanied by