Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Kristian Larsson <kll@swip.net>
To: sup-talk@rubyforge.org
Subject: [sup-talk] Exception when syncing mailbox.
Date: Fri, 25 Dec 2009 18:30:41 +0100	[thread overview]
Message-ID: <20091225173041.GA9253@swip.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]

Hello!

I'm a long time mutt user and just recently heard of sup,
reading its homepage I got hooked just at "If you're the
type of person who treats email as an extension of your
long-term memory, Sup is for you." and so I thought I would
give it a spin.

After installing all the binaries and downloading 0.9, I ran
sup-config to configure the client. A very nice way to get
started, much more so than the config file of mutt which
offers quite a steep entry for usage.

When starting sup, I've noticed some character encoding
problems which I have yet to identify the details of, more
on that when I'll get the client up and running properly.
You see after "a while", it dies by throwing an exception
and it is due to this exception that I write to this list.
Find the exception-log attached. All I've done is configure
the client and try to sync my mailbox, sup will sync som 375
threads and then throw the exception.

What can I do to troubleshoot? Try some later HEAD branch or
something?

Kind regards,
    Kristian.

-- 
Kristian Larsson                                        KLL-RIPE
Network Engineer / Internet Core        Tele2 / SWIPnet [AS1257]
+46 704 264511                                      kll@swip.net

[-- Attachment #2: sup-exception-log.txt --]
[-- Type: text/plain, Size: 746 bytes --]

/usr/lib/ruby/1.8/ferret/index.rb:421:in `[]'
/usr/lib/ruby/1.8/ferret/index.rb:421:in `[]'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/lib/ruby/1.8/ferret/index.rb:413:in `[]'
./sup/ferret_index.rb:257:in `build_message'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
./sup/ferret_index.rb:256:in `build_message'
../bin/sup-sync:149
./sup/poll.rb:151:in `each_message_from'
./sup/imap.rb:197:in `each'
./sup/imap.rb:185:in `upto'
./sup/imap.rb:185:in `each'
./sup/util.rb:560:in `send'
./sup/util.rb:560:in `__pass'
./sup/util.rb:547:in `method_missing'
./sup/poll.rb:139:in `each_message_from'
./sup/util.rb:520:in `send'
./sup/util.rb:520:in `method_missing'
../bin/sup-sync:146
../bin/sup-sync:141:in `each'
../bin/sup-sync:141

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

             reply	other threads:[~2010-01-03 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-25 17:30 Kristian Larsson [this message]
2010-01-05 22:09 ` 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=20091225173041.GA9253@swip.net \
    --to=kll@swip.net \
    --cc=sup-talk@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