Subject: [sup-talk] Crash on saving messages

From: [email-masked] (Alexander Panek)
Date: Thu, 18 Oct 2007 11:32:24 +0200

Hello,

when saving the status (un/read) of my messages (with '$'), sup crashes:

[Thu Oct 18 11:26:51 +0200 2007] stopped cursing
[Thu Oct 18 11:26:51 +0200 2007] oh crap, an exception
[Thu Oct 18 11:26:51 +0200 2007] unlocking /home/jim/.sup/lock...
----------------------------------------------------------------
I'm very sorry, but it seems that an error occurred in Sup. 
Please accept my sincere apologies. If you don't mind, please
send the backtrace below 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
----------------------------------------------------------------

The problem was: 'undefined method `[]' for nil:NilClass' (error type
NoMethodError) A backtrace follows:
/usr/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/imap.rb:272:in
`get_imap_fields': undefined method `[]' for nil:NilClass
(NoMethodError)
from /usr/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/imap.rb:114:in
`unsynchronized_raw_header' from (eval):3:in `raw_header' from
(eval):3:in `synchronize' from (eval):3:in `raw_header'
from /usr/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/imap.rb:105:in
`load_header'
from /usr/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/util.rb:431:in `send'
from /usr/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/util.rb:431:in
`__pass'
from /usr/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/util.rb:420:in
`method_missing' ... 22 levels...
from /usr/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/buffer.rb:193:in
`handle_input' from /usr/lib/ruby/gems/1.8/gems/sup-0.1/bin/sup:195
from /usr/bin/sup:16:in `load' from /usr/bin/sup:16

I am using the gem, version 0.1. Is this fixed in SVN?

Anyways: keep up the good work! :)
-- 
Alexander Panek <alexander.panek at brainsware.org>

---

From: [email-masked] (William Morgan)
Date: Sat, 27 Oct 2007 12:42:09 -0700

> I am using the gem, version 0.1. Is this fixed in SVN?

I think this is the same problem that Ian reported. Should be fixed now
in SVN.

-- 
William <wmorgan-sup at masanjin.net>