From mboxrd@z Thu Jan 1 00:00:00 1970 From: bwalton@artsci.utoronto.ca (Ben Walton) Date: Fri, 04 Sep 2009 16:47:39 -0400 Subject: [sup-talk] more xapian/label woes In-Reply-To: <1252077954-sup-8898@masanjin.net> References: <1252030139-sup-6351@ntdws12.chass.utoronto.ca> <1252077954-sup-8898@masanjin.net> Message-ID: <1252081294-sup-4119@ntdws12.chass.utoronto.ca> Excerpts from William Morgan's message of Fri Sep 04 11:30:11 -0400 2009: > 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? It was with cdb1017, but I likely did have a ~/.sup/xapian directory from previous attempts. I'll try again tonight with that cleared out. > > 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. Ok, I think this is likely the best approach too. Strings and symbols have a somewhat special relationship in ruby though, so I thought it might be ok to force a coercion in that case. Lets make it the last resort as you suggest. 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: