From: jtang@tchpc.tcd.ie (Jimmy Tang)
Subject: [sup-talk] problems with rubymail on an initial sup-add/sync
Date: Wed, 19 Sep 2007 23:44:56 +0100 [thread overview]
Message-ID: <1190241733-sup-1342@vual.tchpc.tcd.ie> (raw)
In-Reply-To: <20070919123616.GA24149@vual.tchpc.tcd.ie>
Hi again
replying to my own mail, i eventually figured out why the previous problem was failing (corrupt mbox's)
but now, this is happening after starting up sup for about 5mins as it scans my mboxes
23:32:23 jtang at vual ~ $ sup
/u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/buffer.rb:32: warning: already initialized constant KEY_ENTER
/u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/buffer.rb:33: warning: already initialized constant KEY_CANCEL
[Wed Sep 19 23:32:25 +0100 2007] locking /u1/trhpc/jtang/.sup/lock...
[Wed Sep 19 23:32:25 +0100 2007] loading index...
[Wed Sep 19 23:32:25 +0100 2007] loaded index of 65133 messages
[Wed Sep 19 23:32:25 +0100 2007] starting curses
[Wed Sep 19 23:41:20 +0100 2007] stopped cursing
[Wed Sep 19 23:41:20 +0100 2007] oh crap, an exception
[Wed Sep 19 23:41:20 +0100 2007] unlocking /u1/trhpc/jtang/.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: 'just added message <200610312309.38117.rj200@ but couldn't find it in a search' (error type RuntimeError)
A backtrace follows:
/u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/index.rb:187:in `sync_message': just added message <200610312309.38117.rj200@ but couldn't find it in a search (RuntimeError)
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/util.rb:401:in `send'
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/util.rb:401:in `method_missing'
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/poll.rb:122:in `add_messages_from'
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/source.rb:93:in `each'
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/util.rb:437:in `send'
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/util.rb:437:in `__pass'
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/util.rb:426:in `method_missing'
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/poll.rb:101:in `add_messages_from'
... 26 levels...
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/modes/thread-index-mode.rb:394:in `load_threads'
from /u1/trhpc/jtang/local/ruby/lib/ruby/gems/1.8/gems/sup-0.1/bin/sup:173
from /u1/trhpc/jtang/local/ruby/bin/sup:16:in `load'
from /u1/trhpc/jtang/local/ruby/bin/sup:16
Thanks,
Jimmy
Excerpts from Jimmy Tang's message of Wed Sep 19 13:36:16 +0100 2007:
> Hi,
>
> I've just installed 0.1 of sup with the current stable version of ruby via gems.
>
> i've just tried adding some of my mbox's and this seems to happen...
>
>
> Scanning mbox:///u1/trhpc/jtang/Mail/system.rancid...
> Scanned 0, added 0, updated 0 messages from
> mbox:///u1/trhpc/jtang/Mail/system.rancid.
> Scanning sup://drafts...
> Scanned 0, added 0, updated 0 messages from sup://drafts.
> Scanning mbox:///u1/trhpc/jtang/Mail/system.RequestTracker...
> ## 2300 (61.25%) read; 0:01:00 elapsed; 0:00:37 remaining
> [Wed Sep 19 13:32:59 +0100 2007] problem getting messages from
> mbox:///u1/trhpc/jtang/Mail/system.RequestTracker: For some bizarre reason,
> RubyMail was unable to parse this message.
> [Wed Sep 19 13:32:59 +0100 2007] problem getting messages from
> mbox:///u1/trhpc/jtang/Mail/system.RequestTracker: For some bizarre reason,
> RubyMail was unable to parse this message.
>
> is there anyway of turning on more debugging to see whats causing the
> problem...?
>
> i tried using -v on the commandline as well but it doesnt seem to say
> anything...
>
>
> Thanks,
> Jimmy
>
--
Jimmy Tang
Trinity Centre for High Performance Computing,
Lloyd Building, Trinity College Dublin, Dublin 2, Ireland.
http://www.tchpc.tcd.ie/ | http://www.tchpc.tcd.ie/~jtang
prev parent reply other threads:[~2007-09-19 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20070919-141338-+042.23-1@vual.tchpc.tcd.ie>
2007-09-19 12:36 ` Jimmy Tang
2007-09-19 14:41 ` William Morgan
2007-09-20 14:31 ` Jimmy Tang
2007-09-20 15:24 ` William Morgan
2007-09-19 22:44 ` Jimmy Tang [this message]
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=1190241733-sup-1342@vual.tchpc.tcd.ie \
--to=jtang@tchpc.tcd.ie \
/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