Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: manish@gslab.com (Manish Sapariya)
Subject: [sup-talk] 'undefined method `longname' for nil:NilClass' (error type NoMethodError)
Date: Wed, 07 Nov 2007 15:05:07 +0530	[thread overview]
Message-ID: <473186CB.8090307@gslab.com> (raw)

This is seen when I run sup. The previous one was with sup-sync.

Looks like some problem with handling encoded messages.
How can I back track?
Thanks,
-Manish


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)
        from /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/poll.rb:157:in 
`add_messages_from'
        from /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/source.rb:93:in 
`each'
        from /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/util.rb:431:in 
`send'
        from /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/util.rb:431:in 
`__pass'
        from /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/util.rb:420:in 
`method_missing'
        from /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/poll.rb:139:in 
`add_messages_from'
        from /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/poll.rb:96:in 
`do_poll'
        from /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/poll.rb:84:in 
`each'
         ... 24 levels...
        from 
/usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/modes/thread-index-mode.rb:431:in 
`load_threads'
        from /usr/lib/ruby/gems/1.8/gems/sup-0.2/bin/sup:193
        from /usr/bin/sup:16:in `load'
        from /usr/bin/sup:16



             reply	other threads:[~2007-11-07  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07  9:35 Manish Sapariya [this message]
2007-11-07 20:39 ` William Morgan
2007-11-08  5:15   ` Manish Sapariya
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=473186CB.8090307@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