From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] Exceptions around saving drafts
Date: Wed, 29 Oct 2008 10:09:57 +0100 [thread overview]
Message-ID: <1225271215-sup-3640@ausone.inria.fr> (raw)
In-Reply-To: <1225160241-sup-4803@entry>
Excerpts from William Morgan's message of Tue Oct 28 03:21:30 +0100 2008:
> Reformatted excerpts from Kevin Riggle's message of 2008-10-26:
> > Working with a draft message today got me lots of exceptions, usually
> > when I saved the draft and went back to my inbox. (These all took the
> > same form, so I've only attached one of them.) Running sup-sync
> > didn't help. Attempting to /delete/ a draft (open the message, hit
> > 'e' on the draft, quit my editor, close the buffer in Sup, hit 'y' for
> > discard) got me a segfault in Ruby (the stock Ubuntu package thereof):
> >
> > ./lib/sup/draft.rb:38: [BUG] Segmentation fault ruby 1.8.6 (2007-09-24) [x86_64-linux]
>
> That don't look good.
>
> > --- EOFError from thread: main
> > End-of-File Error occured at <except.c>:93 in xraise
> > Error occured in compound_io.c:137 - cmpdi_read_i
> > Tried to read past end of file. File length is <1> and tried to read to <30056>
>
> That neither. Any weird situations like running out of disk space?
>
> Have you tried sup-sync -a sup://drafts? That should force a full
> reindex of all your draft messages.
>
> You can also try deleting the message manually through devel/console.sh.
> Search the archives for "console.sh"; I believe there are a few good
> examples of using it.
Yes console.sh is very nice! However the API seems not really designed to be
used that way, maybe a small refactoring with more idiomatic names (like in
rails) would be nice.
ex: Message.find_by_message_id
Message.search(:first, 'is:draft foo bar').destroy!
--
Nicolas Pouillard aka Ertai
prev parent reply other threads:[~2008-10-29 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 22:07 Kevin Riggle
2008-10-27 12:12 ` Nicolas Pouillard
2008-10-28 2:21 ` William Morgan
2008-10-29 9:09 ` Nicolas Pouillard [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=1225271215-sup-3640@ausone.inria.fr \
--to=nicolas.pouillard@gmail.com \
/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