From: chaos@highprogrammer.com (Alan De Smet)
Subject: [sup-talk] fatal exception: invalid contacts.txt
Date: Thu, 14 Feb 2008 15:22:01 -0600 [thread overview]
Message-ID: <20080214212201.GE7284@alpha.monkeycosm.net> (raw)
I'm trying to import a bunch of contacts into sup by directly
modifying the .sup/contacts.txt file. Apparently blank lines and
comments are not welcome. If the goals of contacts.txt include
that humans are able to edit it, blank lines and comments are
helpful and it would be nice if they were allowed. If that's
madness, and only software should edit the file, I'd expect an
error message and more graceful exit.
This is sup v0.4, installed this morning via gem. It (and
rubygems) is installed as a user, not root, on a Red Hat
Enterprise Linux 5 machine.
contents of contacts.txt:
> alice: Alice <alice at example.com>
>
> bob: Bob <bob at example.com>
Output:
> [Thu Feb 14 15:17:25 -0600 2008] using character set encoding "UTF-8"
> [Thu Feb 14 15:17:25 -0600 2008] optional 'chronic' library not found (run 'gem install chronic' to install)
> [Thu Feb 14 15:17:25 -0600 2008] locking /u/a/d/adesmet/.sup/lock...
> [Thu Feb 14 15:17:25 -0600 2008] stopped cursing
> [Thu Feb 14 15:17:25 -0600 2008] oh crap, an exception
> [Thu Feb 14 15:17:25 -0600 2008] unlocking /u/a/d/adesmet/.sup/lock...
> ----------------------------------------------------------------
> I'm very sorry. It seems that an error occurred in Sup. Please
> accept my sincere apologies. If you don't mind, please send the
> contents of sup-exception-log.txt and a brief report of the
> circumstances to sup-talk at rubyforge dot orgs so that I might
> address this problem. Thank you!
>
> Sincerely,
> William
> ----------------------------------------------------------------
> --- RuntimeError from thread: main
> can't parse /u/a/d/adesmet/.sup/contacts.txt line "\n"
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup/contact.rb:18:in `initialize'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup/contact.rb:17:in `foreach'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup/contact.rb:17:in `initialize'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup.rb:96:in `new'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup.rb:96:in `start'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/bin/sup:113
> opt/ruby_gem_home/bin/sup:19:in `load'
> opt/ruby_gem_home/bin/sup:19
contents of sup-exception-log.txt:
> --- RuntimeError from thread: main
> can't parse /u/a/d/adesmet/.sup/contacts.txt line "\n"
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup/contact.rb:18:in `initialize'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup/contact.rb:17:in `foreach'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup/contact.rb:17:in `initialize'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup.rb:96:in `new'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/lib/sup.rb:96:in `start'
> /afs/cs.wisc.edu/u/a/d/adesmet/bin/opt/ruby_gem_home/gems/sup-0.4/bin/sup:113
> opt/ruby_gem_home/bin/sup:19:in `load'
> opt/ruby_gem_home/bin/sup:19
You get very similar output with a contacts.txt file of:
> alice: Alice <alice at example.com>
> # Bob's a nice guy
> bob: Bob <bob at example.com>
--
Alan De Smet http://www.highprogrammer.com/alan
next reply other threads:[~2008-02-14 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 21:22 Alan De Smet [this message]
2008-02-16 13:15 ` 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=20080214212201.GE7284@alpha.monkeycosm.net \
--to=chaos@highprogrammer.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