Comments on: Ferret on Ruby 1.9.1

By: Charles

Charles — Thu, 02 Sep 2010 19:56:26 +0000

I’ll give some more details this weekend once I get back home.

By: Charles

Charles — Thu, 02 Sep 2010 16:35:03 +0000

I was trying the simplest example . I gave up and moved to a Mac Pro…seems to work fine here

By: Stephen Sykes

Stephen Sykes — Sun, 22 Aug 2010 15:14:37 +0000

This looks like the kind of error you get with a corrupted index.

Can you tell me exactly what you are doing to get the error?

By: charles

charles — Fri, 20 Aug 2010 23:44:22 +0000

excuse me, I mean:

C:/Ruby191/lib/ruby/gems/1.9.1/gems/sdsykes-ferret-0.11.6.19/lib/ferret/index.rb:138:in `initialize’: IO Error occured at :117 in xpop_context (IOError)
Error occured in index.c:901 – sis_find_segments_file
Error reading the segment infos. Store listing was

from C:/Ruby191/lib/ruby/gems/1.9.1/gems/sdsykes-ferret-0.11.6.19/lib/ferret/index.rb:138:in `new’
from C:/Ruby191/lib/ruby/gems/1.9.1/gems/sdsykes-ferret-0.11.6.19/lib/ferret/index.rb:138:in `initialize’
from C:/sandbox/ml/test_ferret.rb:8:in `new’
from C:/sandbox/ml/test_ferret.rb:8:in `’

By: charles

charles — Fri, 20 Aug 2010 23:20:32 +0000

I am trying to run ferret on windows XP using Ruby1.91 I have compiled and installed the sdsykes-ferret gem, and it seems to run ok using the RAM disk option. But when I try to specify an index_dir / path, I get the following error:

——————————-

C:/Ruby191/lib/ruby/gems/1.9.1/gems/ferret-0.11.6/lib/ferret/index.rb:138:in `initialize’: IO Error occured at :117 in xpop_context (IOError)
Error occured in index.c:901 – sis_find_segments_file
Error reading the segment infos. Store listing was

from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ferret-0.11.6/lib/ferret/index.rb:138:in `new’
from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ferret-0.11.6/lib/ferret/index.rb:138:in `initialize’
from C:/sandbox/ml/test_ferret.rb:8:in `new’
from C:/sandbox/ml/test_ferret.rb:8:in `’

——————————-

By: Tomash

Tomash — Tue, 08 Jun 2010 08:07:13 +0000

dbalmain has Stephen’s commits in his branch, so maybe we should just ask him to generate a new version of official Ferret gem for all of us to use?

By: Stephen Sykes

Stephen Sykes — Sun, 06 Jun 2010 19:31:34 +0000

Hi Dan,

It’s there, and sdsykes-ferret it is.

-Stephen

By: Dan Kubb

Dan Kubb — Thu, 03 Jun 2010 08:06:39 +0000

Would you mind pushing your gem to rubygems.org as sdsykes-ferret or something? I would love to have my Gemfile conditionally require your gem when under 1.9+, otherwise falling back to using the “official” gem.

By: Stephen Sykes

Stephen Sykes — Thu, 15 Apr 2010 19:58:26 +0000

This is a rails problem, but looks like it will be fixed when 2.3.6 comes out.

https://rails.lighthouseapp.com/projects/8994/tickets/3001-blankslate-is-not-ruby-19-compatible

AAF uses BlankSlate, but it could avoid this. There is a ticket there too:
http://j-k.lighthouseapp.com/projects/45560/tickets/3-rails-232-ruby-191-acts_as_ferret-raises-exception

One possibility for a quick fix would be to redefine BlankSlate in a plugin, using the patches in the rails ticket.

By: Manfred

Manfred — Thu, 15 Apr 2010 19:01:24 +0000

Hi there,
well, the ferret gem does something, most error messages disappear, but one error message still remains after starting the server:

/usr/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.5/lib/active_support/vendor/builder-2.1.2/blankslate.rb:41:in `reveal’: Dont know how to reveal method methods (RuntimeError)

So unfortunately I am still stuck with Suse Linux 11.2 and Ruby 1.9.1 and Rails 2,3,5. what do you recommend? Installing another Ruby version?