Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] new exception
Date: Sat, 05 Sep 2009 15:30:04 -0400	[thread overview]
Message-ID: <1252178309-sup-7297@zyrg.net> (raw)
In-Reply-To: <1252177626-sup-316@ntdws12.chass.utoronto.ca>

Excerpts from Ben Walton's message of Sat Sep 05 15:08:52 -0400 2009:
> --- RuntimeError from thread: main
> DocNotFoundError: No termlist found for document 2478134195
> /usr/lib/ruby/site_ruby/1.8/xapian.rb:239:in `doclength'
> /usr/lib/ruby/site_ruby/1.8/xapian.rb:239:in `postlist'
> /usr/lib/ruby/site_ruby/1.8/xapian.rb:59:in `_safelyIterate'
> /usr/lib/ruby/site_ruby/1.8/xapian.rb:237:in `postlist'
> ./sup/xapian_index.rb:361:in `term_docids'

I'm guessing you're using the Chert Xapian backend. When I moved all the
index data into Xapian it started triggering this Chert bug.
Unfortunately, it's nondeterministic and very hard to reproduce in a
small testcase. I've been holding off filing a bug upstream until I had
a better failing testcase than "run sup-sync". If anyone would like to
familiarize themselves with the xapian-index internals and narrow this
bug down a bit I'd be very glad for the help.

The Flint Xapian backend seems to work fine, so for now I suggest using that.


  reply	other threads:[~2009-09-05 19:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05 19:08 Ben Walton
2009-09-05 19:30 ` Rich Lane [this message]
2009-09-05 19:35   ` Ben Walton
2009-09-05 19:55     ` Rich Lane
2009-09-05 21:57       ` Ben Walton
2009-09-06 17:02         ` Rich Lane
2009-09-06 17:22           ` Ben Walton

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=1252178309-sup-7297@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