similar to: Warning encoding error after Ferret changesets 765-769

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

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

Hey ... while davebalmain.com is not renewed (and who knows when that is going happen), i''ve put the 0.11.4 API rdocs online at: http://api.omdb-beta.org/ferret/index.html Ben

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

Hey folks, ** 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 + rails -jewelry) and phrase queries ("the quick brown fox") as well as some more

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

There is serious memory leak bug in ferret. I''m having this error on TextDrive Container (aka. Joyent Accelerators) OpenSolaris with Ferret 0.11.4 It happens while searching for some terms with accented or special characters. This makes ferret to allocate lots of memory (usually reaching 3+ GB) and failing if another query like this is executed. Any ideas on that, could this be locale

Hey folks, I''ve just put another release up. I''ve mostly just fixed some stability and memory leak issues. The most notable change is the probably the addition of a win32 gem to make life a little easier for all those Windows users out there. Also, I''ve added an index browser. Just try running; > ferret-browser path/to/index and then visit;

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:

I have spent days trying to figure out how to get UTF-8 working with my site. Here''s my environment: Linux version 2.6.16.29-xen_3.0.3.0 Ruby 1.8.4 (2005-12-24 [i386-linux] Rails 1.2.3 mongrel (1.0.1) mongrel_cluster (1.0.2, 0.2.1) ferret (0.11.4) acts_as_ferret stable plugin Ferret DRB server When I don''t use an analyzer with my acts_as_ferret declaration, everything works

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

Firstly, thanks Dave for all your hard work. Ferret Rocks!, I am just testing 0.11.4.win32 and it seems to work just fine, however the index creation phase of my app is perhaps 3x slower under 0.11.4 vs 0.10.9 Details follow: System: windows xp sp2, index on local hard disk, Ruby 1.8.6 Run #1, Ferret 0.10.9 - Reboot - Build index, 35,000 rows added in 297 seconds - Run #2, Ferret 0.11.4 -

Hi ferreters: I''ve already posted this in rails, but someone there suggested this would be better. I''m getting a ferret error when I try to delete any item that has been previously indexed. I just installed ferret, so the indexes aren''t big or anything. What I''m trying to do is to just delete an item on a table that has been index. Here''s the error

I found it quite fun to generate index by ferret. However, I had to use lucene now. Can I use the index that I''ve already done by ferret? ps. Lucene 2.2.0 vs Ferret 0.11.4 Thx! -- Posted via http://www.ruby-forum.com/.

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

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

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

Hi- I was previously using 0.11.4, and I wrote my own analyzer. Everything worked fine. When I took the system to production, 0.11.4 starting failing updating the index, complaining that files were missing. The failure always happened on the same model document, and was completely reproducible. This failure looked a lot like the one described at http://www.ruby-forum.com/topic/104145. I

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