From: manish@gslab.com (Manish Sapariya)
Subject: [sup-talk] 'undefined method `longname' for nil:NilClass' (error type NoMethodError)
Date: Thu, 08 Nov 2007 10:45:09 +0530 [thread overview]
Message-ID: <47329B5D.4090907@gslab.com> (raw)
In-Reply-To: <1194467915-sup-5870@south>
Hi Williams,
Thanks for the fix. However looks like I have some weird mail in my box.
The body and the charset both are nil. Is there any way I can backtrack the
offending message and find out whats the character set and encoding used
for that message?
Thanks,
Manish
(rdb:1) list
[372, 381] in /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/message.rb
372 def self.convert_from body, charset
373 begin
374 raise MessageFormatError, "RubyMail decode returned a null
body" unless body
375 return body unless charset
376 Iconv.iconv($encoding, charset, body).join
377 rescue Errno::EINVAL, Iconv::InvalidEncoding,
Iconv::IllegalSequence, MessageFormatError => e
378 Redwood::log "warning: error (#{e.class.name}) decoding
message body from #{charset}: #{e.message}"
379 File.open("sup-unable-to-decode.txt", "w") { |f| f.write
body }
380 body
381 end
(rdb:1) p m.charset
nil
(rdb:1) p m.body
nil
William Morgan wrote:
> Excerpts from Manish Sapariya's message of Wed Nov 07 01:35:07 -0800 2007:
>
>> The problem was: 'undefined method `longname' for nil:NilClass' (error
>> type NoMethodError)
>> A backtrace follows:
>> /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/poll.rb:102:in `do_poll': undefined method `longname' for nil:NilClass (NoMethodError)
>>
>
> This should be fixed in SVN now. You may have to re-index the offending
> source (sup-sync --all <source uri>).
>
>
next prev parent reply other threads:[~2007-11-08 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 9:35 Manish Sapariya
2007-11-07 20:39 ` William Morgan
2007-11-08 5:15 ` Manish Sapariya [this message]
2007-11-09 19:13 ` 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=47329B5D.4090907@gslab.com \
--to=manish@gslab.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