Subject: [sup-talk] Endless loop when using chronic extension straight from git

From: Stanislav Ochotnicky <[email-masked]>
Date: Fri, 18 Mar 2011 07:32:31 +0100

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 <[email-masked]>
Software Engineer - Base Operating Systems Brno

PGP: 7B087241
Red Hat Inc.                               http://cz.redhat.com
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Paul Grove <[email-masked]>
Date: Fri, 18 Mar 2011 09:57:31 +0000

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