From: Marc Hartstein <marc.hartstein@alum.vassar.edu>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Exception crashing sup
Date: Tue, 26 Apr 2011 16:43:21 -0400 [thread overview]
Message-ID: <1303850166-sup-9964@cabinet> (raw)
In-Reply-To: <BANLkTikmgj+kTR6+6OKHo03car9j5nGdrg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1067 bytes --]
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("<message_id>") 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).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-04-26 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 17:03 Marc Hartstein
2011-04-26 20:43 ` Marc Hartstein [this message]
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=1303850166-sup-9964@cabinet \
--to=marc.hartstein@alum.vassar.edu \
--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