similar to: outstanding patches

I can consistently segfault the 0.10.4 gem, so I''m trying to get the subversion version working with hopes towards tracking the problem down. I have a fresh SVN checkout but: a) the version (in ferret.rb) claims to be 0.9.6; and b) Ferret::Index::FieldInfos and a couple other classes are missing at run time. It looks like this is because they''re not exported in the C

Hi Dave, The patch below corrects a buffer overflow bug in q_parser.y. Since it is triggered by excessively long query strings, I believe that this bug could be exploited to allow arbitrary code execution if a query string supplied by a user is passed in directly to Ferret and not truncatated. If I''m right, you should consider a new release asap. I''ve fixed it to simply

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

Hi Dave & co, I''ve got a couple Sup users who encounter the following error fairly consistently, even with 0.11.4. After they see this, the index is not recoverable and they have to rebuild from scratch. Any ideas? --- cut here --- /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:726:in `initialize'': IO Error occured at <except.c>:93 in xraise (IOError) Error

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

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

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, We''re using Ferret 0.9.4 and we''ve observed the following behavior. Searching for ''fieldname: foo and bar'' works fine while ''fieldname: "foo and bar"'' doesn''t return any results. Is there a way to make ferret recognize the ''and'' inside the query as a search term and not an operator? (I hope I got the

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

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

Is there any somewhat standard way to remove or otherwise handle special or syntax characters from a user''s search, such as a colon? I was thinking maybe there was something akin to Ferret::Analysis::FULL_ENGLISH_STOP_WORDS, like Ferret::Analysis::FERRET_SYNTAX_CHARS, but no such luck. How are other folks dealing with filtering user input? John

We were using ferret (with acts_as_ferret) on our production boxes. Everything was going OK for a few days then we got a seg fault from it that brought down the box. The specs: * Rails 1.1.6 * Ruby 1.8.4 * Ferret 0.10.6 * RedHat ES 3 * Apache * Pound * 5 instances of Mongrel Can ferret handle multiple processes accessing it''s files at the same time? Not that we were doing this (but

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

Hi all, At the bottom of chapter 8 of the tutorial, on the topic of closures, mentions that there are "often better ways to implement these features than explicit stack frames". Does anyone know what techniques this cryptic statement might be referring to? Thanks! -- William <wmorgan-llvm at masanjin.net>

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

Welcome all. Feel free to use this list for any comments, bug reports, or patches pertaining to RubyTorrent. The RubyForge site is up: http://rubyforge.org/projects/rubytorrent/, and anonymous CVS is enabled. -- William <wmorgan-rubytorrent-devel@masanjin.net>

Hi all, I''ve been spending a lot of time over the past few weeks on RubyTorrent. All the changes are in CVS. Highlights are: - Transfer speeds should be much better, thanks to a better piece selection algorithm, and being more aggressive about dropping boring peers and adding new ones, - Download/upload rate limits now work. - Many bugs fixed. - .torrent creation now

Hi everyone, I''m pretty new to Lucene and Ferret, so I feel that this is most likely myself not completely understanding the correct way to do this. I haved indexed ~2200 text files (of various sizes), and I am now running searches on the index to get a feel for Lucene and Ferret. In my first program, which is using Lucene I search for ''influenza'' and get the

I''ve installed the latest version of Ferret (0.10.13) on Mac OS X 10.4.8 (Tiger) and I''m developing using Locomotive2. I installed with: $ gem install ferret I have a ferret_test.rb file: ----begin--------- require ''rubygems'' require ''ferret'' include Ferret index = Index::Index.new(:path => ''/opt/search-index'')