From: Steve Goldman <sgoldman@tower-research.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Problems running sup-convert-ferret-index
Date: Tue, 26 Jan 2010 22:24:34 -0500 [thread overview]
Message-ID: <1264562538-sup-9933@sgoldmanlinux.tower-research.com> (raw)
In-Reply-To: <1264510235-sup-2915@masanjin.net>
Excerpts from William Morgan's message of Tue Jan 26 08:00:02 -0500 2010:
> Reformatted excerpts from Steve Goldman's message of 2010-01-25:
> > Presumably. I run it through sup-config, which outputs "Rats, that
> > didn't work" when the return code is non-zero. But sup-sync outputs
> > nothing.
>
> And just to confirm, when you run that sup-sync command by itself,
> outside of sup-config, it just dies without a backtrace, right?
Correct.
> Since this didn't happen with Ferret, my best guess is that the problem
> lies somewhere in the bowels of Xapian or the bindings thereof:
>
> > xapian-bindings-ruby-1.0.17-2.fc11.x86_64
>
> I would try and get the latest xapian-full gem. I have no experience
> with the bindings Fedora distributes, but I know that that gem works for
> me and for others.
>
> It's possible to install and run gems entirely out of your home
> directory (at least in recent versions), so it should be possible to do
> this without involving your sysadmin, if that's easier.
>
> Something like:
>
> gem install gemcutter
> gem install xapian-full
>
> Ought to magically work, if your gems are new enough.
Do I need to do something to make ruby use this xapian and not the
Fedora xapian? How can I tell which it is using?
> > He says the Fedora release will likely get there soon, but we could
> > try to get it in advance if you think this will help.
>
> Let's wait on playing with Ruby versions until we have your Xapian
> bindings locked down.
I did some sleuthing and found that it hangs on the loop over all the
messages in my first source (imap) after it gets through exactly seven
of them. Specifically, it hangs at the top of the loop:
Redwood::PollManager.each_message_from source do |m|
Any ideas?
Thanks.
--
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
prev parent reply other threads:[~2010-01-27 3:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 19:50 Steve Goldman
2010-01-17 20:38 ` William Morgan
2010-01-17 21:22 ` Steve Goldman
2010-01-17 21:34 ` William Morgan
2010-01-17 23:38 ` Steve Goldman
2010-01-18 0:04 ` William Morgan
2010-01-18 0:28 ` Steve Goldman
2010-01-18 1:44 ` Steve Goldman
2010-01-18 2:10 ` Rich Lane
2010-01-18 6:03 ` Anirudh Sanjeev
2010-01-18 17:04 ` William Morgan
2010-01-18 17:27 ` Anirudh Sanjeev
2010-01-18 19:43 ` Steve Goldman
2010-01-18 22:05 ` William Morgan
2010-01-19 13:31 ` Steve Goldman
2010-01-19 13:37 ` William Morgan
2010-01-25 16:34 ` Steve Goldman
2010-01-25 21:30 ` William Morgan
2010-01-25 21:56 ` Steve Goldman
2010-01-26 13:00 ` William Morgan
2010-01-27 3:24 ` Steve Goldman [this message]
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=1264562538-sup-9933@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