From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Mysterious nil errors
Date: Tue, 09 Mar 2010 23:52:45 -0500 [thread overview]
Message-ID: <1268196678-sup-9427@ezyang> (raw)
In-Reply-To: <1268196562-sup-1692@ezyang>
Actually, I know precisely where this is from:
Content-Type:
Content-Disposition: inline
Content-Transfer-Encoding: base64
RT-Attachment: 1176783/16113169/7868621
Which translates into an empty string and thus the following
trace:
--- NoMethodError from thread: poll after loading inbox
undefined method `downcase' for nil:NilClass
/usr/lib/ruby/gems/1.8/gems/rmail-1.0.0/lib/rmail/header.rb:537:in `content_type'
/home/ezyang/Dev/sup/lib/sup/message.rb:439:in `message_to_chunks'
/home/ezyang/Dev/sup/lib/sup/message.rb:439:in `map'
/home/ezyang/Dev/sup/lib/sup/message.rb:439:in `message_to_chunks'
/home/ezyang/Dev/sup/lib/sup/message.rb:244:in `load_from_source!'
/home/ezyang/Dev/sup/lib/sup/message.rb:340:in `build_from_source'
/home/ezyang/Dev/sup/lib/sup/poll.rb:163:in `each_message_from'
/home/ezyang/Dev/sup/lib/sup/maildir.rb:160:in `each'
[snip]
I suppose this is something that should be fixed on the rmail side...
Cheers,
Edward
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-03-10 4:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 4:50 Edward Z. Yang
2010-03-10 4:52 ` Edward Z. Yang [this message]
2010-03-10 6:43 ` Tero Tilus
2010-03-10 17:24 ` Rich Lane
2010-03-10 17:40 ` Edward Z. Yang
2010-03-10 17:59 ` Rich Lane
2010-03-10 18:06 ` Edward Z. Yang
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=1268196678-sup-9427@ezyang \
--to=ezyang@mit.edu \
--cc=sup-devel@rubyforge.org \
/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