similar to: error at index.c:901

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 just installed ferret for the first time and integrated it with my app. On my dev machine it''s fine but on my production server I get this when I call find_by_contents(): Processing LinksController#results (for 24.185.105.59 at 2007-03-28 05:28:36) [POST] Session ID: 3f2dc7c17147c0e52178ba697a119833 Parameters: {"commit"=>"Search",

I have a large index (~6GB, ~1 million docs) that was built by RDig. I wrote a script to iterate through the index to clear out some duplicate information to try to reduce the size of the index. clients.each {|client| docs = RDig.searcher.search("+supplier_id:#{client.id}") docs.each {|doc| data = doc[:data].dup #the contents of the web page new_results = {}

Hi all, I''ve ran into a problem with Ferret on my rails app, and I don''t really have a clue about why. When running the unit tests, I get the following error output: > Exception raised: > Class: <NoMethodError> > Message: <"You have a nil object when you didn''t expect it!\nThe > error occured while evaluating nil.version"> >

I''m getting a segmentation fault on a large index (15GB). I''m running ferret 0.11.4 on OpenSuSE 10.2 with ruby 1.8.6. The segmentation fault appeared after I optimized the index, see further below for the error message I got before that. Ferret works perfectly on other (smaller) indexes. Is this a known issue, and if so, is there a workaround? --------------------- after

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

I''m developing locally on Windows and I have a remote dev box that runs Linux. I''m trying to use RDig just to index using urls, no files. Both use acts_as_ferret for an administrative search that works fine. On the Windows machine, I get no errors, but get no results. On the Linux machine, I get: File Not Found Error occured at <except.c>:93 in xraise Error occured in

Here''s the status of the patch for Ruby that solves the freezing issue on Windows. ----- Forwarded message from "U.Nakamura" <usa@garbagecollect.jp> ----- Date: Sun, 6 Feb 2005 14:58:19 +0900 From: "U.Nakamura" <usa@garbagecollect.jp> To: ruby-core@ruby-lang.org Subject: Re: windows socket connection freeze Hello, In message "windows socket

I am trying to use highlight, but I am getting this kind of thing: /usr/local/lib/ruby/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:197:in `highlight'': IO Error occured at <except.c>:93 in xraise (IOError) Error occured in index.c:1222 - lazy_df_get_bytes len = -5, but should be greater than 0 from

Hello Dave, Hello all, I''ve got this error because I try to search something and sort it by name : Argument Error occured at <except.c>:93 in xraise Error occured in sort.c:551 - field_cache_get_index Cannot sort by field "name". It doesn''t exist in the index. The problem, occur when my index is empty, so the field "name" does not exists. --

I''m getting an exception when I query a large index (4GB, ~700K docs) on a particular field. For example: supplier_id:77490 IO Error occured at <except.c>:93 in xraise (IOError) Error occured in fs_store.c:293 - fsi_seek_i seeking pos -1515676213: <Invalid argument> Anecdotally it seems to happen for supplier_ids > 76900. Here is the field info for that

Matz claims 1.8.3 might be released in April. If we''re lucky, maybe it will have the Windows socket connection fix applied. (Although the patch has been hanging around since last June... but maybe they just needed some prodding. :) ) Then RubyTorrent will be much more usable on Windows. ----- Forwarded message from Yukihiro Matsumoto <matz@ruby-lang.org> ----- Date: Tue, 8 Feb

Hi All, I'm in the process of setting up samba with ldap and winbind and haven't been able to find an article anywhere on how to do this. I've managed to troll together everything except the directory setup. I'm stuck on what I need to add into the directory (ldif files) to make it all go. I've included the steps I took and so hopefully it'll be easy to spot what

In a rails script (something in the "script" dir with the good require) I added many document (around 4000) to an index globaly instanciate (and build if not present) in config/environment.rb. I ran 3 three times my script (I deleted my index every time before), and only the third was successful. That was STRANGE ! :) These are the errors :

And now, for some news about the only Ferret project that doesn''t involve Rails: sup version 0.0.7 has been released! http://sup.rubyforge.org Sup is a console-based email client that combines the best features of GMail, mutt, and emacs. Sup matches the power of GMail with the speed and simplicity of a console interface. Sup makes it easy to: - Handle massive amounts of email. -

Where tha Dave at? I''ve got 3 outstanding patches I''d like to see committed, or at least get some feedback on. -- William <wmorgan-ferret at masanjin.net>

Do you use rubies to read your emails? Well, sup version 0.0.1 has been released! http://sup.rubyforge.org Sup is an attempt to take the UI innovations of web-based email readers (ok, really just GMail) and to combine them with the traditional wholesome goodness of a console-based email client. Sup is designed to work with massive amounts of email, potentially spread out across different mbox

Hi, Using the 0.10.4 gem under ruby 1.8.5 (2006-08-25) [i686-linux], I get different results with a TermQuery and a search string. Namely, using a search string seems to always work whereas using a TermQuery often doesn''t return any entries. For example: > x=@i[450][:message_id] => "9e7db9110509070759732b21c4 at mail.gmail.com" >

Hi all, I''m going to do my best to spend some time on RubyTorrent over the next week or so. Here''s what I plan to accomplish: 1. gem packaging 2. Slight API changes: move to Net::BitTorrent rather than RubyTorrent; remove the requirement for ''self'' being passed to on_event (not very Rubyish IMO); etc. 3. Add UDP tracker support. 4. ri documentation I

I''m happy to announce RubyTorrent 0.3, which I''ve decided is good enough to be called a beta. :) >From http://rubytorrent.rubyforge.org/: RubyTorrent is a pure-Ruby BitTorrent peer library and toolset. You can use it to download or serve files over BitTorrent from any Ruby program. RubyTorrent is released under the GNU GPL. Note that RubyTorrent doesn''t include a