From: Gaute Hope <eg@gaute.vetsj.com>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Bug: Xapian exception after having polled
Date: Sun, 4 Oct 2009 12:15:50 +0200 [thread overview]
Message-ID: <20091004101550.GA7330@qwerzila.bluecom.no> (raw)
In-Reply-To: <1254594099-sup-719@zyrg.net>
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
Greetings,
Applied; fails at the same point, new backtrace attached.
(ps: your patch fails with 'git am' might be the Author: line that
should be a From:)
- gaute
On Sat, Oct 03, 2009 at 02:22:34PM -0400, Rich Lane wrote:
> Apply the attached patch and let us know what the new backtrace is.
[-- Attachment #2: exception-log.txt --]
[-- Type: text/plain, Size: 2750 bytes --]
--- RuntimeError from thread: poll after loading inbox
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/poll.rb:146:in `each_message_from'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/source.rb:104:in `each'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/util.rb:560:in `send'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/util.rb:560:in `__pass'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/util.rb:547:in `method_missing'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/poll.rb:139:in `each_message_from'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/poll.rb:93:in `do_poll'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/poll.rb:81:in `each'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/poll.rb:81:in `do_poll'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/poll.rb:80:in `synchronize'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/poll.rb:80:in `do_poll'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/util.rb:520:in `send'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/util.rb:520:in `method_missing'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/modes/poll-mode.rb:15:in `poll'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/poll.rb:48:in `poll'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/util.rb:520:in `send'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/util.rb:520:in `method_missing'
/home/gaute/.gem/ruby/1.8/gems/sup-999/bin/sup:196
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup.rb:77:in `reporting_thread'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup.rb:75:in `initialize'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup.rb:75:in `new'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup.rb:75:in `reporting_thread'
/home/gaute/.gem/ruby/1.8/gems/sup-999/bin/sup:196
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:669:in `call'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:669:in `__unprotected_load_threads'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:610:in `call'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:610:in `load_n_threads_background'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup.rb:77:in `reporting_thread'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup.rb:75:in `initialize'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup.rb:75:in `new'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup.rb:75:in `reporting_thread'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:608:in `load_n_threads_background'
/home/gaute/.gem/ruby/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:679:in `__unprotected_load_threads'
(eval):12:in `load_threads'
/home/gaute/.gem/ruby/1.8/gems/sup-999/bin/sup:196
/home/gaute/.gem/ruby/1.8/bin/sup:19:in `load'
/home/gaute/.gem/ruby/1.8/bin/sup:19
next prev parent reply other threads:[~2009-10-04 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 10:36 gauteh
2009-10-03 18:22 ` Rich Lane
2009-10-04 10:15 ` Gaute Hope [this message]
2009-10-04 18:45 ` Rich Lane
2009-10-04 18:56 ` Gaute Hope
2009-10-04 19:03 ` Rich Lane
2009-10-04 19:20 ` Gaute Hope
2009-10-05 22:01 ` Gaute Hope
2009-10-06 10:14 ` Guillaume Quintard
2009-10-06 13:34 ` Gaute Hope
2009-10-06 14:59 ` 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=20091004101550.GA7330@qwerzila.bluecom.no \
--to=eg@gaute.vetsj.com \
--cc=rlane@club.cc.cmu.edu \
--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