From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.92.18 with SMTP id p18cs153755agb; Tue, 6 Oct 2009 08:53:39 -0700 (PDT) Received: by 10.224.110.135 with SMTP id n7mr1454186qap.185.1254844419061; Tue, 06 Oct 2009 08:53:39 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 13si8939182qyk.26.2009.10.06.08.53.38; Tue, 06 Oct 2009 08:53:39 -0700 (PDT) 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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id A5BE316782AE; Tue, 6 Oct 2009 11:53:38 -0400 (EDT) X-Greylist: delayed 343 seconds by postgrey-1.31 at rubycentral.org; Tue, 06 Oct 2009 11:53:31 EDT Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by rubyforge.org (Postfix) with ESMTP id AED5E1858204 for ; Tue, 6 Oct 2009 11:53:31 -0400 (EDT) Received: by ewy3 with SMTP id 3so756342ewy.7 for ; Tue, 06 Oct 2009 08:53:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:subject:from:to :in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=6mebinrif0S0/gwKNiv9pGopbOFYfOcN6/rduPA4Q+o=; b=E3eJgNzjngkE7voD0QDIryN39rp0N2Cmxm7yaF0QLGIG3cegebj4FIUWGX+5f+Egfn wiGqM4vq8yAwOd7cSAk0iNTXGE+GamyZUagneeWEBXKPrgrEXOUcedPTSYYAJHOH6CPN lDfsnArnyCsho33MSZZYvjlpzsbH9sRGOkrSk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:subject:from:to:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding; b=mDXANDi0VHl+JVjI8h0aDEQ11saQACcApRfWsEssaB3F+s4hnPU0kqSG/pDjI+hQG/ Ov+ylDOtPaXC8S7b3c8cAUa7QA6BVkAjfT5XipFKe/lXCtr0oc7JiMg+ScIxTgJOI7s8 ySYUNtf3zshy9qRp788ExIUYrDiGi5Cle90dk= Received: by 10.216.18.209 with SMTP id l59mr389450wel.7.1254844410936; Tue, 06 Oct 2009 08:53:30 -0700 (PDT) Received: from localhost (physnat56.physics.umass.edu [128.119.50.56]) by mx.google.com with ESMTPS id x6sm17035325gvf.9.2009.10.06.08.53.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 06 Oct 2009 08:53:30 -0700 (PDT) From: Ben Gamari To: sup-talk In-reply-to: <1254844050-sup-4148@ben-laptop> References: <1254844050-sup-4148@ben-laptop> Date: Tue, 06 Oct 2009 11:53:18 -0400 Message-Id: <1254844166-sup-1028@ben-laptop> User-Agent: Sup/git Subject: Re: [sup-talk] Crash while in thread-view-mode 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 Well, it seems like whatever caused the crash earlier did something to my index. Now any attempt to open a thread-index-mode of my LKML label (which I was viewing in the earlier crash) causes the client to immediately crash. Do any of the sup utilities have any sort of index sanity checker to find potential causes of this sort of issue? Thanks, - Ben --- RuntimeError from thread: load threads for thread-index-mode wrong id called on nil /opt/exp/sup/lib/sup.rb:17:in `id' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:225:in `update' /usr/lib64/ruby/1.8/rubygems/custom_require.rb:31:in `sort_by' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:225:in `each' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:225:in `sort_by' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:225:in `update' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:223:in `synchronize' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:223:in `update' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:628:in `__unprotected_load_n_threads' /opt/exp/sup/lib/sup/thread.rb:334:in `load_n_threads' /opt/exp/sup/lib/sup/xapian_index.rb:117:in `each_id_by_date' /opt/exp/sup/lib/sup/xapian_index.rb:110:in `each_id' /opt/exp/sup/lib/sup/xapian_index.rb:110:in `each' /opt/exp/sup/lib/sup/xapian_index.rb:110:in `each_id' /opt/exp/sup/lib/sup/xapian_index.rb:117:in `each_id_by_date' /opt/exp/sup/lib/sup/thread.rb:328:in `load_n_threads' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:625:in `__unprotected_load_n_threads' (eval):12:in `load_n_threads' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:609:in `load_n_threads_background' /opt/exp/sup/lib/sup.rb:77:in `reporting_thread' /opt/exp/sup/lib/sup.rb:75:in `initialize' /opt/exp/sup/lib/sup.rb:75:in `new' /opt/exp/sup/lib/sup.rb:75:in `reporting_thread' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:608:in `load_n_threads_background' /opt/exp/sup/lib/sup/modes/thread-index-mode.rb:679:in `__unprotected_load_threads' (eval):12:in `load_threads' /opt/exp/sup/lib/sup/modes/label-search-results-mode.rb:33:in `spawn_nicely' /opt/exp/sup/lib/sup/modes/label-list-mode.rb:103:in `select_label' /opt/exp/sup/lib/sup/mode.rb:51:in `send' /opt/exp/sup/lib/sup/mode.rb:51:in `handle_input' /opt/exp/sup/lib/sup/buffer.rb:267:in `handle_input' /usr/bin/sup:239 Excerpts from Ben Gamari's message of Tue Oct 06 11:47:34 -0400 2009: > I just had sup crash on me while reading a thread. Not really sure what > to make of the backtrace. Looks like it failed during polling but who > knows why. Thanks, > > - Ben > _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk