* [sup-talk] Endless loop when using chronic extension straight from git
@ 2011-03-18 6:32 Stanislav Ochotnicky
2011-03-18 9:57 ` Paul Grove
0 siblings, 1 reply; 2+ messages in thread
From: Stanislav Ochotnicky @ 2011-03-18 6:32 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 1021 bytes --]
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?
--
Stanislav Ochotnicky <sochotnicky@redhat.com>
Software Engineer - Base Operating Systems Brno
PGP: 7B087241
Red Hat Inc. http://cz.redhat.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [sup-talk] Endless loop when using chronic extension straight from git
2011-03-18 6:32 [sup-talk] Endless loop when using chronic extension straight from git Stanislav Ochotnicky
@ 2011-03-18 9:57 ` Paul Grove
0 siblings, 0 replies; 2+ messages in thread
From: Paul Grove @ 2011-03-18 9:57 UTC (permalink / raw)
To: sup-talk
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-03-18 10:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-18 6:32 [sup-talk] Endless loop when using chronic extension straight from git Stanislav Ochotnicky
2011-03-18 9:57 ` Paul Grove
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox