similar to: Ferret 0.11.2-rc3 released

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, 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

Hello! I am developing a rails application in a test environment on Windows XP and recently upgraded to InstantRails 1.5. During the upgrade process, I went to install the latest ferret gem and realized that the latest gem compiled for Windows was 10.9. We upgraded our production environment (Ubuntu) to 11.1-rc2 successfully, but wanted to find out if we were going to run into any problems

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 +

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''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

Hi, I have a largish index [700MB] which is updated from time to time, requiring me to close and recreate the Ferret::Search::Searcher to use the latest index. My problem is that the first few searches on the new index are slow [by comparison to before the close/recreate], I''m guessing because the new index is being loaded into RAM by my OS and into Ferret as needed. I''m

Hello Dave, Hello all, Some weeks ago, Maz submit a patch to quickly dump or load a ferret database in an other format to prevent index rebuilding (due to changes in the format) or to simplify backup/replication tasks. I re-paste this patch (it was against the 0.10.14) here : http://pastie.caboo.se/43603 Do you think it''s intresting for ferret ? Do you have any plan for this patch ?

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:

Hey guys, Just released Ferret 0.11.1. Hopefully this will fix *most* of the problems people were having. Now that I know gcc hides stack overflows on Ubuntu because -fstack-protector is set, I won''t get caught by that one again. Anyone know any other gotchas I should be aware of on Ubuntu. Please try the new version and let me know if you are still having problems with it. I have until

Hi, Just downloaded the new ferret 0.11. I''m on OSX btw. I get this error everytime I run my unit tests: Loaded suite ferret_updater_unit_test Started E/usr/local/lib/ruby/1.8/erb.rb:504: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i686-darwin8.7.1] Abort trap When I revert back to 10.14 I dont get this error. When I comment out the line: Ferret::Index::Index.new({:path =>

Hello, Ferret created a 4.5GB> index file. $ 4534029210 2007-02-26 12:46 _el.cfs The creation of the index went smoothly. Searching through this index also works fine. However whenever I try to get the contents of an indexed document I get an error when the document number is above 621108: irb(main):080:0> searcher[621108].load IOError: IO Error occured at <except.c>:79 in xraise

Just a quick note for future reference - at least for me, ferret won''t work on Ruby 1.8.4. gem install ferret Successfully installed ferret-0.11.4-mswin32 ruby -v ruby 1.8.4 (2005-12-24) [i386-mswin32] irb irb(main):001:0> require ''ferret'' A windows error message box appears - ruby.exe - Entry Point Not Found The procedure entry point rb_w32_write could not be

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

i have this error when i try to install ferret C:\Documents and Settings\>gem install ferret Need to update 6 gems from http://gems.rubyforge.org ...... complete Building native extensions. This could take a while... ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError) ERROR: Failed to build gem native extension. ruby extconf.rb install ferret creating Makefile nmake

Hi, Using aaf to search pages, I wanted to present excerpts from the texts even when more than one term was used in the search. I came to some results, despite the difficulty caused by Unicode+ruby. The last problem I''m faced is to get the query words, without the logical articulation chars if any. Is there a clean way to get them ? -- Jean-Christophe Michel

Hi, There is a problem with the way that acts_as_ferret verifies the index is valid. In ensure_index_exists it looks for a file named ''segments''. With the 0.11.0 release of ferret there is no file with this name. On my dummy application I have a ''segments.gen'' and ''segments_2y''. Changing the test to segments.gen fixes the problem that the

Hi folks, I''ve working and playing with acts_as_ferret and follow this fantastic tutorial: http://www.railsenvy.com/2007/2/19/acts-as-ferret-tutorial When I try to implement the field storage tip, it crash. So, I try to make it via script/console: 1. I have a simple model called Articles: class Article < ActiveRecord::Base acts_as_ferret :fields =>

Hi, i''m working on a project using Ferret for indexing it''s datas. I''m very happy with it but i need to code an extension to implement a .to_json method to TopDocs class, because ruby''s json implementation is really really slow... It''s my second (the first was the tutorial :/ ) ruby C extension, so i''m not really at ease with ruby C