From: Paul Grove <paul.a.grove@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Endless loop when using chronic extension straight from git
Date: Fri, 18 Mar 2011 09:57:31 +0000 [thread overview]
Message-ID: <1300442123-sup-1862@localhost> (raw)
In-Reply-To: <1300429882-sup-6298@sochotnicky.usersys.redhat.com>
I have also got this problem, Although I havnt looked into it, I cannot
use on:, after:, and such for fear of it failing.
I am also using the latest sup from git
Excerpts from Stanislav Ochotnicky's message of Fri Mar 18 06:32:31 +0000 2011:
> I encountered this weird endless loop when I was trying to hack on sup
> a bit and using it at the same time.
>
> I have a shell script that looks more-less like this:
> -------------------
> #!/bin/sh
> export SUP_LOG_LEVEL=debug
> cd ~/projects/sup
> ruby -I lib bin/sup
> ----------------
>
> Normal usage/searching is OK, but when I run sup like that and do
> query like "after:(2 days ago)" sup goes into endless loop (with ruby
> CPU use going to 100%). I also have to kill off the remaining ruby
> process (as in -SIGKILL). When I try to do the same with sup already
> installed with "gem install sup" everything works as expected.
>
> Note that I can reproduce this even with 0.12.1 tag checked out in git
> so it's not my changes that are causing this.
>
> It seems like I am doing something terribly wrong here. Any idea what
> that might be?
>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-03-18 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 6:32 Stanislav Ochotnicky
2011-03-18 9:57 ` Paul Grove [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=1300442123-sup-1862@localhost \
--to=paul.a.grove@gmail.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