From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] Crash while syncing
Date: Sat, 29 Aug 2009 12:25:33 -0400 [thread overview]
Message-ID: <1251563082-sup-3525@zyrg.net> (raw)
In-Reply-To: <cd67f63a0908290503g37ab5575ibb6162d06f7528af@mail.gmail.com>
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?
next prev parent reply other threads:[~2009-08-29 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 9:18 Nicolas Pouillard
2009-08-29 12:03 ` Nicolas Pouillard
2009-08-29 16:25 ` Rich Lane [this message]
2009-08-29 16:45 ` Nicolas Pouillard
2009-08-29 16:59 ` Rich Lane
2009-08-29 17:05 ` Nicolas Pouillard
2009-08-30 0:22 ` Rich Lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1251563082-sup-3525@zyrg.net \
--to=rlane@club.cc.cmu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox