* [sup-talk] sup crash after a reply
@ 2009-12-15 22:10 Vernon Mauery
2009-12-19 19:08 ` William Morgan
0 siblings, 1 reply; 2+ messages in thread
From: Vernon Mauery @ 2009-12-15 22:10 UTC (permalink / raw)
To: sup-talk
I am running the latest git version of sup (as of yesterday) and I
imported my 70000+ emails, archived most of them and have started
to receive and send new mails. I just replied to a message, was
reading other messages in that thread, and then went back to the
index listing with 'x' and I got this crash. In the mean time, it
is possible that the message I just sent had made it to the mailing
list and back to me before going back to the message index. I am
not sure on that. But here is the backtrace:
[Tue Dec 15 14:01:29 -0800 2009] ERROR: oh crap, an exception
----------------------------------------------------------------
I'm very sorry. It seems that an error occurred in Sup. Please
accept my sincere apologies. If you don't mind, please send the
contents of /home/vhmauery/.sup/exception-log.txt 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
----------------------------------------------------------------
--- ArgumentError from thread: periodic poll
:(null) isn't a valid argument for IndexReader.get_document(index)
/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 `[]'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/ferret_index.rb:257:in `build_message'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/ferret_index.rb:256:in `build_message'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/util.rb:520:in `send'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/util.rb:520:in `method_missing'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:95:in `do_poll'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:154:in `each_message_from'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/maildir.rb:160:in `each'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/maildir.rb:157:in `upto'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/maildir.rb:157:in `each'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/util.rb:560:in `send'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/util.rb:560:in `__pass'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/util.rb:547:in `method_missing'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:142:in `each_message_from'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:94:in `do_poll'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:82:in `each'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:82:in `do_poll'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:81:in `synchronize'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:81:in `do_poll'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/util.rb:520:in `send'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/util.rb:520:in `method_missing'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/modes/poll-mode.rb:15:in `poll'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:48:in `poll'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:65:in `start'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup.rb:77:in `reporting_thread'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup.rb:75:in `initialize'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup.rb:75:in `new'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup.rb:75:in `reporting_thread'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/poll.rb:62:in `start'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/util.rb:520:in `send'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/lib/sup/util.rb:520:in `method_missing'
/home/vhmauery/.gem/ruby/1.8/gems/sup-0.9.1/bin/sup:209
/home/vhmauery/.gem/ruby/1.8/bin/sup:19:in `load'
/home/vhmauery/.gem/ruby/1.8/bin/sup:19
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [sup-talk] sup crash after a reply
2009-12-15 22:10 [sup-talk] sup crash after a reply Vernon Mauery
@ 2009-12-19 19:08 ` William Morgan
0 siblings, 0 replies; 2+ messages in thread
From: William Morgan @ 2009-12-19 19:08 UTC (permalink / raw)
To: sup-talk
Reformatted excerpts from Vernon Mauery's message of 2009-12-15:
> I am running the latest git version of sup (as of yesterday) and I
> imported my 70000+ emails, archived most of them and have started to
> receive and send new mails.
I am going to throw this bug report in the big bucket of "weird Ferret
issues that will go away once we stop using Ferret."
In the mean time, you may want to switch to the Xapian backend.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-12-19 19:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-12-15 22:10 [sup-talk] sup crash after a reply Vernon Mauery
2009-12-19 19:08 ` William Morgan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox