From mboxrd@z Thu Jan  1 00:00:00 1970
From: rlane@club.cc.cmu.edu (Rich Lane)
Date: Sat, 29 Aug 2009 12:25:33 -0400
Subject: [sup-talk] Crash while syncing
In-Reply-To: <cd67f63a0908290503g37ab5575ibb6162d06f7528af@mail.gmail.com>
References: <cd67f63a0908290218g30a737a9pd46d902cdf5399bb@mail.gmail.com>
	<cd67f63a0908290503g37ab5575ibb6162d06f7528af@mail.gmail.com>
Message-ID: <1251563082-sup-3525@zyrg.net>

Excerpts from Nicolas Pouillard's message of Sat Aug 29 08:03:04 -0400 2009:
> On Sat, Aug 29, 2009 at 11:18 AM, Nicolas
> Pouillard<nicolas.pouillard at gmail.com> wrote:
> > Hello,
> >
> > While doing a from scratch sup-sync to benefit for the new version of
> > the xapian index, sup-sync
> > crashed like this:
> >
> 
> I've lauched sup-sync on another bunch of mboxes and got this crash at the end:
> 
> Deleting missing messages from the index...
> /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:17:in `id': wrong id
> called on nil (RuntimeError)
>         from /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:237
>         from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:150:in
> `each_message'
>         from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/xapian_index.rb:141:in
> `each_id'
>         from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/xapian_index.rb:141:in
> `each'
>         from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/xapian_index.rb:141:in
> `each_id'
>         from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:149:in
> `each_message'
>         from /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:235
>         from /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:233:in `each'
>         from /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:233
>         from /usr/bin/sup-sync:19:in `load'
>         from /usr/bin/sup-sync:19
> 

Are you using the Flint or Chert Xapian backend?