From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs327952ebc; Sun, 17 Jan 2010 08:06:42 -0800 (PST) Received: by 10.224.89.196 with SMTP id f4mr3689990qam.90.1263744401478; Sun, 17 Jan 2010 08:06:41 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 6si9696695qwk.51.2010.01.17.08.06.41; Sun, 17 Jan 2010 08:06:41 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 01A2E18582DE; Sun, 17 Jan 2010 11:06:41 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 8EED818582CB for ; Sun, 17 Jan 2010 11:06:33 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NWXe5-0002sh-A7 for sup-talk@rubyforge.org; Sun, 17 Jan 2010 11:06:33 -0500 From: William Morgan To: sup-talk In-reply-to: <4B4EB5A9.8050001@exys.org> References: <4B4EB5A9.8050001@exys.org> Date: Sun, 17 Jan 2010 11:06:33 -0500 Message-Id: <1263744149-sup-2441@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] trying sup again, couple of crashes, etc X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hi Arvid, Sorry to hear about your negative experience. Sounds like it's several unrelated issues all adding up. Reformatted excerpts from Arvid Picciani's message of 2010-01-14: > The interface only responds to shift-q. Typing only "q" will prompt and > that prompt can not be answered with y Y ^y sane for the ^C prompt. Sounds like you're using Ruby 1.9. You can either use Ruby 1.8, sup next (bleeding-edge code, as you see below), or wait for Sup 0.10. > So i went to the git next tree: It takes 30 seconds to start on a > core2, and uses 100% cpu polling for new messages apparantly. Screen > is flooded with ruby warnings, so it is unusable. Can you run sup-sync before running Sup the first time? Adding new messages does take a lot of CPU, but it's typically only an issue if you have to add lots of documents. > /home/aep/kram/mainline/lib/sup/xapian_index.rb:52:in `save_index': > undefined method `flush' for nil:NilClass (NoMethodError) Fixed in next already. Sorry about that. > --- NoMethodError from thread: poll after loading inbox > undefined method `[]' for nil:NilClass > /home/aep/kram/mainline/lib/sup/xapian_index.rb:570:in `mkterm' > /home/aep/kram/mainline/lib/sup/xapian_index.rb:345:in `find_docid' I believe this is also fixed in next. Please try again. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk