From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] EOFError crash
Date: Thu, 06 Nov 2008 16:06:02 +0100 [thread overview]
Message-ID: <1225983752-sup-1166@ausone.inria.fr> (raw)
In-Reply-To: <1225981048-sup-9011@blackpad>
Excerpts from Eduardo Habkost's message of Thu Nov 06 15:33:23 +0100 2008:
> Excerpts from William Morgan's message of Wed Nov 05 15:48:34 -0200 2008:
> > Reformatted excerpts from Decklin Foster's message of 2008-11-02:
> > > This just happened again. Should I put it into ditz or something? (I
> > > feel exceedingly lame, but I don't have time to debug it today
> > > either.)
> >
> > No. Sadly, this is one of the innumerable Ferret errors that crop up
> > from time to time, which spurred STS.
>
> I've been easily reproducing crashes similar to this one. The only thing
> I need to reproduce it is making sure I load another label while sup is
> still polling for new messages.
>
> If I deliver a lot of new messages to a maildir source and don't run
> sup-sync, sup will spend a few seconds loading the new messages and
> there is plenty of time to hit L, go to a label (I don't know if it
> needs to be the same label the new messages being loaded are getting),
> and see the crash.
I rarely use 'L', however I often search for particular set of mails
using '\', maybe it's a general problem with search during poll.
In this case perhaps making sup a little bit more sequential would make
it more robust (this could help us to wait for STS).
Best regards,
--
Nicolas Pouillard aka Ertai
next prev parent reply other threads:[~2008-11-06 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 18:42 Decklin Foster
2008-11-02 17:40 ` Decklin Foster
2008-11-05 17:48 ` William Morgan
2008-11-06 14:33 ` Eduardo Habkost
2008-11-06 15:06 ` Nicolas Pouillard [this message]
2008-11-06 21:40 ` William Morgan
2008-11-07 2:52 ` Eduardo Habkost
2008-11-07 6:21 ` William Morgan
2008-11-07 11:32 ` Eduardo Habkost
2008-11-07 13:08 ` Eduardo Habkost
2008-11-10 3:59 ` William Morgan
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=1225983752-sup-1166@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