Excerpts from Rich Lane's message of Sat Sep 05 15:30:04 -0400 2009: > 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.
Your guess is as good as mine here...I didn't realize there were different back ends. How would I go about switching? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting.
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
