From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.169.74 with SMTP id ac10cs7409vdc; Fri, 18 Mar 2011 03:09:12 -0700 (PDT) Received: by 10.43.54.200 with SMTP id vv8mr1209547icb.378.1300442952044; Fri, 18 Mar 2011 03:09:12 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id vr19si7993089icb.0.2011.03.18.03.09.11; Fri, 18 Mar 2011 03:09:12 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 8B8693C8040; Fri, 18 Mar 2011 06:09:11 -0400 (EDT) Received: from mail-wy0-f178.google.com (mail-wy0-f178.google.com [74.125.82.178]) by rubyforge.org (Postfix) with ESMTP id A596E1858381 for ; Fri, 18 Mar 2011 05:57:36 -0400 (EDT) Received: by wyj26 with SMTP id 26so4215157wyj.23 for ; Fri, 18 Mar 2011 02:57:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:subject:from:to:in-reply-to :references:date:message-id:user-agent:content-transfer-encoding; bh=A2cQBD0WGL03moBk7w8yjB/KgFGi0TmSs/TV7Y+e/as=; b=WHJ5qt+X1dsRh/EvjjrB+NqKrn/3WtKhuKxmbjQnt8NcZdYt/d5vVroQdS0YWSqUVU u8kj1DPxCinMeiSGulWxqIXRBtVYU55HihjFvTIg5Sb5GwhB2RK/wvzxuVuhAoxO2nIA ry1fc3plRvDSzqAbO4nSbaR70EGufaZDh7ir8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:subject:from:to:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding; b=xEQ0Y0iNjy3KkgB/yTtxLHmLXVwN8hNZ7K0cncQ3z8Mv1QLMnfgHcsKO4PEKMA4F7I s+o8h+V+4Z9T6/bwsxsERYLpIA/Q3Uzmp/H8DViFU/1sMYcpO4KwWascvpvNoi3q6zmY azvvey9aYwdT3HOa1W1J3YNtcg+on4baZmzAE= Received: by 10.227.208.202 with SMTP id gd10mr1031832wbb.23.1300442255918; Fri, 18 Mar 2011 02:57:35 -0700 (PDT) Received: from localhost (78-86-196-163.zone2.bethere.co.uk [78.86.196.163]) by mx.google.com with ESMTPS id o6sm1237659wbo.54.2011.03.18.02.57.34 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Mar 2011 02:57:35 -0700 (PDT) From: Paul Grove To: sup-talk In-reply-to: <1300429882-sup-6298@sochotnicky.usersys.redhat.com> References: <1300429882-sup-6298@sochotnicky.usersys.redhat.com> Date: Fri, 18 Mar 2011 09:57:31 +0000 Message-Id: <1300442123-sup-1862@localhost> User-Agent: Sup/git Subject: Re: [sup-talk] Endless loop when using chronic extension straight from git X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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