From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] more xapian/label woes
Date: Fri, 04 Sep 2009 08:30:11 -0700 [thread overview]
Message-ID: <1252077954-sup-8898@masanjin.net> (raw)
In-Reply-To: <1252030139-sup-6351@ntdws12.chass.utoronto.ca>
Reformatted excerpts from Ben Walton's message of 2009-09-03:
> I get exceptions with non-Symbol labels being passed around again. To
> finish the import of my ferret dumpfile, I had to do the following:
Is this with a recent next, and after deleting any vestigal
~/.sup/xapian directory and .db files? If so, there really shouldn't be
any label issues. If there are, can you attach the original exception?
Also, does your sources.yaml file have something weird for labels?
> This got me to the point where I could fire up sup with
> SUP_INDEX=xapian, but the initial poll caused the attached exception.
> I wonder if LabelManager should simply call .to_sym (.intern) on
> everything passed to it?
Certainly an option, but I'm hoping to keep the "fail fast" behavior for
now since it is revealing underlying problems.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-09-04 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 2:13 Ben Walton
2009-09-04 15:30 ` William Morgan [this message]
2009-09-04 20:47 ` 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=1252077954-sup-8898@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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