From: dom.lobue@gmail.com (Dominic LoBue)
Subject: [sup-talk] sup crash while attempting to load next email after deleting previous
Date: Fri, 5 Jun 2009 05:35:15 -0700 [thread overview]
Message-ID: <93de24940906050535p7178dedctc9f9f8c166acdf2e@mail.gmail.com> (raw)
Hello,
Sup just crashed on me. The last thing I did was do ,d to delete the
email I was viewing and move on to the next. I had deleted several
other emails previously in the exact same way with no problems.
The only thing that may matter is that I had over 1000 threads loaded
in the index view (I get a _lot_ of email at work :( ).
I'm using a git release made from the below commit:
commit a8869f951cf8ec3a4a50492290c9ca757c968f49
Author: William Morgan <wmorgan-sup at masanjin.net>
Date: Sun May 31 08:58:16 2009 -0700
yet another utf8 bugfix: fix string subsetting
... with a HORRIBLE SLOW HACK!
And here is the exception-log:
--- NoMethodError from thread: load messages for thread-view-mode
undefined method `date' for nil:NilClass
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:783:in
`text_for_thread_at'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:752:in
`regen_text'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:346:in `map_with_index'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:641:in `each_with_index'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:346:in `each'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:346:in `each_with_index'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:346:in `map_with_index'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:752:in
`regen_text'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:228:in
`update'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:202:in
`handle_deleted_update'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/update.rb:27:in `send'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/update.rb:27:in `relay'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/update.rb:27:in `each'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/update.rb:27:in `relay'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:505:in `send'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:505:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-view-mode.rb:431:in
`delete_and_then'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-view-mode.rb:451:in
`dispatch'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:119:in
`call'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:119:in
`select'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:71:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:69:in `initialize'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:69:in `new'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:69:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:99:in
`select'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:149:in
`launch_another_thread'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:131:in
`launch_next_thread_after'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-view-mode.rb:457:in
`dispatch'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-view-mode.rb:429:in
`delete_and_then'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-view-mode.rb:404:in
`delete_and_next'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:50:in `send'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:50:in `handle_input'
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/buffer.rb:249:in `handle_input'
/usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup:238
/usr/bin/sup:19:in `load'
/usr/bin/sup:19
Dominic
reply other threads:[~2009-06-05 12:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=93de24940906050535p7178dedctc9f9f8c166acdf2e@mail.gmail.com \
--to=dom.lobue@gmail.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