From: Stanislav Ochotnicky <sochotnicky@redhat.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Endless loop when using chronic extension straight from git
Date: Fri, 18 Mar 2011 07:32:31 +0100 [thread overview]
Message-ID: <1300429882-sup-6298@sochotnicky.usersys.redhat.com> (raw)
[-- 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
next reply other threads:[~2011-03-18 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 6:32 Stanislav Ochotnicky [this message]
2011-03-18 9:57 ` Paul Grove
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=1300429882-sup-6298@sochotnicky.usersys.redhat.com \
--to=sochotnicky@redhat.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