From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.188.165 with SMTP id gb5cs191309vdc; Tue, 26 Apr 2011 14:35:14 -0700 (PDT) Received: by 10.224.105.139 with SMTP id t11mr1085218qao.282.1303853713871; Tue, 26 Apr 2011 14:35:13 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id l14si252566qck.151.2011.04.26.14.35.12; Tue, 26 Apr 2011 14:35: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 5ED8118583A9; Tue, 26 Apr 2011 17:35:12 -0400 (EDT) Received: from mail-qw0-f50.google.com (mail-qw0-f50.google.com [209.85.216.50]) by rubyforge.org (Postfix) with ESMTP id CA8A918583A8 for ; Tue, 26 Apr 2011 16:43:29 -0400 (EDT) Received: by qwe5 with SMTP id 5so685990qwe.23 for ; Tue, 26 Apr 2011 13:43:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:subject:from:to:in-reply-to:references :date:message-id:user-agent:content-transfer-encoding:mime-version :content-type; bh=tzw4ZO2wgiHp0drN0pdDjxWy43QP8rIfrP4PuBSXP6s=; b=giX2SePuBM+QDcowXbc7anRiRxsEcB3WYMbAQrSsj0KH6pmeAWPM9J5JDi1bMMm6c6 JOg+7b0kA+nBAqfZxWifoYemvuH2Z/zKa227VQHTNxkcI18aeHbxfBVj/3yzYImWMDh+ SJINqac8nYPwyKGbnJXJ3n0nvZp1mRfbkpz4k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:from:to:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding:mime-version:content-type; b=QIHx3OtQMSG30lxmJSsq+SA+8bM9cXLcXaTqEI85hXREWiNgQ7nSwVshK5n4e4t8pQ 5NiGlu1LOFPaU7mGoRSW3tp4Vf48ZR9ezqhsb3lybHR2rfd6JfpVaZeU5obQzl+sQIYq aVoAszM8IQupy1Rl2pb32mQRvj2pEYbjvqjTo= Received: by 10.224.190.68 with SMTP id dh4mr1061826qab.256.1303850609475; Tue, 26 Apr 2011 13:43:29 -0700 (PDT) Received: from cabinet.magus.is-a-geek.com (108-64-13-253.lightspeed.wlfrct.sbcglobal.net [108.64.13.253]) by mx.google.com with ESMTPS id g28sm68266qck.39.2011.04.26.13.43.28 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2011 13:43:28 -0700 (PDT) Received: by cabinet.magus.is-a-geek.com (Postfix, from userid 1000) id F3FB930C14A; Tue, 26 Apr 2011 16:43:26 -0400 (EDT) From: Marc Hartstein To: sup-talk In-reply-to: References: Date: Tue, 26 Apr 2011 16:43:21 -0400 Message-Id: <1303850166-sup-9964@cabinet> User-Agent: Sup/git MIME-Version: 1.0 Subject: Re: [sup-talk] Exception crashing sup 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: , Content-Type: multipart/mixed; boundary="===============0295061648==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org --===============0295061648== Content-Transfer-Encoding: 8bit Content-Type: multipart/signed; boundary="=-1303850606-590893-6601-2341-1-="; protocol="application/pgp-signature" --=-1303850606-590893-6601-2341-1-= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Excerpts from Marc Hartstein's message of Tue Apr 26 13:03:19 -0400 2011:= > Something happened causing sup to crash, and now I get this exception > every time I try to start. I'm currently tracking master. Finally got it (though that outgoing message is lost because I foolishly deleted it earlier; but that's ok, it wasn't that important anyway). The message_id for the problem message appears to have appeared twice in a row in the index. This caused find_docid to fail, ungracefully. Going into the devel console, finding the message id, and doing Index.delete("") appears to have cleared things up nicely. I believe the problem may have been caused in the first place by my impatiently pressing ^L while a message was still sending. Not sure why this would have this effect, but that was what I did when it crashed. The outgoing message was GPG-signed, which might be relevant. Sorry I didn't think to preserve the message for analysis. Although it appears it made it out to gmail and out to the recipient (and it looks fine). --=-1303850606-590893-6601-2341-1-= Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk23Lm4ACgkQSEext8NjodvEHgCfZxQxpNywgKeq1HItnr/in+6q 5PsAn2YYBXh1Lpd11rayFveJzLfo1Ng6 =VjOP -----END PGP SIGNATURE----- --=-1303850606-590893-6601-2341-1-=-- --===============0295061648== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk --===============0295061648==--