From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] crash when sup-syncing to xapian
Date: Tue, 18 Aug 2009 13:35:35 -0400 [thread overview]
Message-ID: <1250616603-sup-5612@ntdws12.chass.utoronto.ca> (raw)
I just tried to import my index to xapian and it crashed part way
through the import. I then discovered that I couldn't use ferret
either. There is something wonky with label handling, as per attached
exception log. I haven't had a chance to look at the code yet, but
I'll poke at it tonight.
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.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sup-exception-log.txt
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090818/28bccae3/attachment.txt>
next reply other threads:[~2009-08-18 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 17:35 Ben Walton [this message]
2009-08-18 18:20 ` Benoît PIERRE
2009-08-18 18:42 ` Rich Lane
2009-08-18 19:17 ` Benoît PIERRE
2009-08-18 19:52 ` Rich Lane
2009-08-18 20:14 ` Benoît PIERRE
2009-08-19 0:03 ` Ben Walton
2009-08-19 18:39 ` William Morgan
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=1250616603-sup-5612@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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