From mboxrd@z Thu Jan  1 00:00:00 1970
From: rlane@club.cc.cmu.edu (Rich Lane)
Date: Sat, 05 Sep 2009 15:30:04 -0400
Subject: [sup-talk] new exception
In-Reply-To: <1252177626-sup-316@ntdws12.chass.utoronto.ca>
References: <1252177626-sup-316@ntdws12.chass.utoronto.ca>
Message-ID: <1252178309-sup-7297@zyrg.net>

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.