From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] sources.yaml labels
Date: Sun, 06 Sep 2009 09:47:06 -0400 [thread overview]
Message-ID: <1252244621-sup-3579@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1252242820-sup-1452@masanjin.net>
Excerpts from William Morgan's message of Sun Sep 06 09:22:21 -0400 2009:
> The former is "correct". But if you put in the latter, it should be
> converted automatically, and written out as the former when you exit
> Sup.
Ok, so my sources.yaml is 'good.'
> I'm a little disturbed that you're still seeing problems with this. Can
> you confirm that SerializeLabelsNicely#after_unmarshal! (source.rb circa
> line 167) is being run in your sources after they're loaded from
> sources.yaml? That should ensure that you end up with a Set of symbols
> when Sup's running, regardless of what's in the file.
Yes, I added a debug in that method and saw a message for each source.
> The other source of bad labels is the serialized version of the messages
> stored by Xapian, if you use Xapian. But if you've regenerated your
> Xapian index recently, this shouldn't be a problem...
I generated this about 2 days ago with a current (at the time) head of
next.
> It strikes me now that the other possible source of non-symbol labels is
> a hook like before-add. Are you using that to call Message#add_label
> with a string argument, by any chance?
I was doing this. I had a hook from my very early sup days still in
play. Since it was actually completely redundant (procmail filtering
and autolabelling via sources) now, I've simply removed it.
> If none of the above, can you post the latest version of the exceptions
> you're seeing?
I still can't load sup without coercing strings to symbols in the <<
method though. The exception log is attached (from a clean startup).
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: exception-log.txt
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090906/8e8d8383/attachment.txt>
-------------- 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/8e8d8383/attachment.bin>
next prev parent reply other threads:[~2009-09-06 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 0:19 Ben Walton
2009-09-06 13:22 ` William Morgan
2009-09-06 13:47 ` Ben Walton [this message]
2009-09-06 14:16 ` Ingmar Vanhassel
2009-09-06 14:07 ` Ben Walton
2009-09-06 15:06 ` William Morgan
2009-09-06 15:26 ` Ben Walton
2009-09-06 16:41 ` 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=1252244621-sup-3579@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