From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] new exception
Date: Sun, 06 Sep 2009 13:22:39 -0400 [thread overview]
Message-ID: <1252257711-sup-2477@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1252255655-sup-2460@zyrg.net>
Excerpts from Rich Lane's message of Sun Sep 06 13:02:19 -0400 2009:
> Well, that's not good. How often does this bug occur? What version of
> Xapian are you running? How many messages are in your index?
It's only occurred twice, but both were with my polluted index of ~77k
messages. Let me run for a bit now that I've cleaned out my string
labels and see what happens.
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 --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090906/5f1cedfa/attachment.bin>
prev parent reply other threads:[~2009-09-06 17:22 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
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 [this message]
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=1252257711-sup-2477@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