From: benoit.pierre@gmail.com (Benoît PIERRE)
Subject: [sup-talk] crash when sup-syncing to xapian
Date: Tue, 18 Aug 2009 22:14:49 +0200 [thread overview]
Message-ID: <1250626302-sup-2408@localdomain> (raw)
In-Reply-To: <1250624577-sup-4801@zyrg.net>
Excerpts from Rich Lane's message of Tue Aug 18 21:52:12 +0200 2009:
> Excerpts from Beno?t PIERRE's message of Tue Aug 18 15:17:03 -0400 2009:
>
> [...]
>
> It'd be nice to get a backtrace including the offending caller. I'd just
> replace the warn with a fail.
The problem comes from my ~/.sup/sources.yaml file, the labels for a source
are not symbols:
hash:
relapse: true
music: true
After converting them to symbols it works:
hash:
:relapse: true
:music: true
--
A: Because it destroys the flow of conversation.
Q: Why is top posting dumb?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090818/94c721f9/attachment.bin>
next prev parent reply other threads:[~2009-08-18 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 17:35 Ben Walton
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 [this message]
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=1250626302-sup-2408@localdomain \
--to=benoit.pierre@gmail.com \
/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