sup talk - Mar 2011 - Endless loop when using chronic extension straight from git

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 at redhat.com>
Software Engineer - Base Operating Systems Brno

PGP: 7B087241
Red Hat Inc.                               http://cz.redhat.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL:
<http://rubyforge.org/pipermail/sup-talk/attachments/20110318/c3d142de/attachment-0001.bin>

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?
>