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: Tue, 27 Oct 2009 08:14:50 -0400	[thread overview]
Message-ID: <1256645659-sup-3884@sgoldmanlinux.tower-research.com> (raw)
In-Reply-To: <1256637386-sup-8828@tilus.net>

Excerpts from Tero Tilus's message of Tue Oct 27 05:58:47 -0400 2009:
> Steve Goldman, 2009-10-26 22:15:
> > 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'
> 
> http://gitorious.org/sup/mainline/blobs/master/lib/sup/ferret_index.rb#line260
> 
> Looks like Sup cant find the source for a message (appearing in
> results?).  Have you altered your sources lately?  Afaik you might
> need to rebuild your index.
> 

No, it can find it.  But sometimes it takes a long time.

Is there some sort of timeout built into the polling process that
could cause a crash?
-- 

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-27 12:15 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
2009-10-27  9:58 ` Tero Tilus
2009-10-27 12:14   ` Steve Goldman [this message]
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=1256645659-sup-3884@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