Subject: [sup-talk] scary exception

From: [email-masked] (John Bent)
Date: Sun, 26 Apr 2009 21:28:27 -0600

On Friday, sup stopped loading and crashed with an exception, I also
couldn't run sup-sync.  At first I was a little scared, but then I
remembered that sup doesn't actually modify mail data so that I could
revert to pine, and then I got very, very scared.

I though I would have to do weird things at a ruby prompt but I just
waited two days and now it works again.  Somewhat strange since I tried
about five times on Friday.  Oh well, I'm running sup in screen so I'll
just never quit again.  :)

Here's the error message in case there's something obvious to someone
else:

tangerine:~/mail>sup-sync
[Fri Apr 24 16:43:10 -0600 2009] using character set encoding "US-ASCII"
[Fri Apr 24 16:43:11 -0600 2009] crypto: no gpg binary detected
[Fri Apr 24 16:43:11 -0600 2009] locking /Users/johnbent/.sup/lock...
[Fri Apr 24 16:43:11 -0600 2009] loading index...
[Fri Apr 24 16:43:11 -0600 2009] loaded index of 79908 messages
Scanning mbox:/Users/johnbent/mail/mbox...
[Fri Apr 24 16:43:11 -0600 2009] unlocking /Users/johnbent/.sup/lock...
/opt/local/lib/ruby/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:768:in
`search': IO Error occured at <except.c>:93 in xraise (IOError)
Error occured in fs_store.c:284 - fsi_read_i
    couldn't read 1024 chars from : <Unknown error: 0>

    from
/opt/local/lib/ruby/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:768:in
`do_search'
    from
/opt/local/lib/ruby/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:339:in
`search'
    from /opt/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
    from
/opt/local/lib/ruby/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:338:in
`search'
    from
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:422:in
`load_entry_for_id'
    from /opt/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
    from
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:421:in
`load_entry_for_id'
    from
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:499:in `send'
     ... 10 levels...
    from /opt/local/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:131:in
`each'
    from /opt/local/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:131
    from /opt/local/bin/sup-sync:16:in `load'
    from /opt/local/bin/sup-sync:16

Thanks,

JOHn

---

From: [email-masked] (William Morgan)
Date: Mon, 27 Apr 2009 10:25:19 -0700

Hi John,

>     couldn't read 1024 chars from : <Unknown error: 0>

It appears that you're running off a gem generated directly from the git
repo. How recently did you do that? This Ferret error is something I
though we had kicked quite a while ago, so if you are running from a
recent git, I'll be worried.
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (John Bent)
Date: Mon, 27 Apr 2009 11:34:54 -0600

> recent git, I'll be worried.
I'm sorry.  I don't remember.  The timestamp on my sup executable says
Jan 13 2009.  I'll try to upgrade and see if I ever see this again.  

John

---

From: [email-masked] (William Morgan)
Date: Mon, 27 Apr 2009 10:46:43 -0700

> Jan 13 2009.  I'll try to upgrade and see if I ever see this again.  

Yeah, I think it was around March that things got merged in. Try it with
the latest & greatest and see if it happens again.
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (John Bent)
Date: Sat, 23 May 2009 23:54:42 -0600

> the latest & greatest and see if it happens again.
Ok, I figured out what the problem was.  I used to be able to stay
current with git pull; rake gem; sudo gem install pkg/sup-999.gem.  But
with a new work proxy and my inability to get git to work w/ a proxy, I
switched to:

git clone http://git.gitorious.org/sup/mainline.git

Then I couldn't figure out how to make a gem in mainline or install so I
just figured out I could approximate an install by copying bin/* into my
path . . . forgot the lib.  Anyway, I got the scary exception again and
looked at exception-log.txt and realized I had a mismatch with my libs.
So now I'm doing the git clone mainline thing and using ruby -l lib -w
bin/sup.

Anyway, at the risk of embarrassing myself, I wanted to get this info
out there in case some other poor schlub wanders down my same convoluted
path. 

Thanks,

John

---

From: [email-masked] (William Morgan)
Date: Wed, 27 May 2009 09:03:13 -0700

Reformatted excerpts from John Bent's message of 2009-05-23:
> Then I couldn't figure out how to make a gem in mainline or install

These operations should all be the same, regardless of whether you're
cloning the git:// uri or the http:// one.

> So now I'm doing the git clone mainline thing and using ruby -l lib -w

Sup does maintain different version numbers for bin/sup and lib/sup.rb,
and checks for a mismatch, but that's not useful for different versions
from git, since they all claim version "git".

Oh well, glad it works now.
-- 
William <wmorgan-sup at masanjin.net>