Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Steve Goldman <sgoldman@tower-research.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Can't search without crashing
Date: Mon, 26 Oct 2009 19:30:20 -0400	[thread overview]
Message-ID: <1256599752-sup-9794@sgoldmanlinux.tower-research.com> (raw)
In-Reply-To: <1256588053-sup-8922@sgoldmanlinux.tower-research.com>


It's not every time.

Here's my theory: my mail sits on a server across a network.  When I
can access that data *quickly*, sup doesn't crash.  When the network
(or file system or whatever) takes longer, sup crashes.

Can anyone back that up?

Thanks.


Excerpts from Steve Goldman's message of Mon Oct 26 16:15:04 -0400 2009:
> 
> Wow, I guess I haven't tried to search in a while... I can't search
> for *anything* without it crashing hard.  Every time.  I'm on master.
> 
> Anyone??
> 
> 
> --- RuntimeError from thread: load threads for thread-index-mode
> invalid source 4
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/ferret_index.rb:260:in
> `build_message'
> /apps/home/sgoldman/lib/ruby/1.8/monitor.rb:242:in `synchronize'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/ferret_index.rb:256:in
> `build_message'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/ferret_index.rb:163:in
> `each_id_by_date'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/thread.rb:332:in `call'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/thread.rb:332:in
> `load_n_threads'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/ferret_index.rb:163:in
> `each_id_by_date'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/ferret_index.rb:162:in `each'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/ferret_index.rb:162:in
> `each_id_by_date'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/thread.rb:328:in
> `load_n_threads'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/thread-index-mode.rb:625:
> in `__unprotected_load_n_threads'
> (eval):12:in `load_n_threads'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/thread-index-mode.rb:609:
> in `load_n_threads_background'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup.rb:77:in `reporting_thread'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup.rb:75:in `initialize'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup.rb:75:in `new'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup.rb:75:in `reporting_thread'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/thread-index-mode.rb:608:
> in `load_n_threads_background'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/thread-index-mode.rb:679:
> in `__unprotected_load_threads'
> (eval):12:in `load_threads'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/thread-index-mode.rb:81:i
> n `initialize'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/line-cursor-mode.rb:22:in
>  `call'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/line-cursor-mode.rb:22:in
>  `initialize'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/line-cursor-mode.rb:22:in
>  `each'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/line-cursor-mode.rb:22:in
>  `initialize'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/line-cursor-mode.rb:19:in
>  `new'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/line-cursor-mode.rb:19:in
>  `initialize'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/thread-index-mode.rb:54:i
> n `initialize'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/search-results-mode.rb:6:
> in `initialize'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/search-results-mode.rb:30
> :in `new'
> /apps/infrafs1/sgoldman/sup-src/mainline/lib/sup/modes/search-results-mode.rb:30
> :in `spawn_from_query'
> bin/sup:275
> -- 
> 
> Steve Goldman
> sgoldman@tower-research.com
> 
> T: 212.219.6014
> F: 212.219.6007
> 
> Tower Research Capital, LLC
> 377 Broadway, 11th Fl.
> New York, NY 10013
-- 

Steve Goldman
sgoldman@tower-research.com

T: 212.219.6014
F: 212.219.6007

Tower Research Capital, LLC
377 Broadway, 11th Fl.
New York, NY 10013
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2009-10-26 23:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 20:15 Steve Goldman
2009-10-26 23:30 ` Steve Goldman [this message]
2009-10-27  9:58 ` Tero Tilus
2009-10-27 12:14   ` Steve Goldman
2009-11-01 16:32 ` William Morgan
2009-11-01 16:48   ` Steve Goldman
2009-11-01 17:23     ` 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=1256599752-sup-9794@sgoldmanlinux.tower-research.com \
    --to=sgoldman@tower-research.com \
    --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