From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] IMAP server restart causes Sup exception
Date: Tue, 20 May 2008 09:05:59 -0700 [thread overview]
Message-ID: <1211299258-sup-2226@south> (raw)
In-Reply-To: <1211295759-sup-614@tomsk>
Reformatted excerpts from Marcus Williams's message of 2008-05-20:
> I should pipe up here as well - this exception was one of the reasons
> I switched to offlineimap as I would get it randomly in sup during
> imap actions. I couldnt figure out how they interacted with each other
> though as it didnt happen enough to debug :(
Interesting. I've had weird issues in the past with the Ruby IMAP
library and threading, so this might be related. I've definitely seen it
generate nonsensical backtraces by funny exception handling across
threads.
Simultaneous dependencies on 20 libaries of dubious quality---that's the
story of Sup.
Well once I get up the energy to write SupServer, I won't have to
support anything except for mbox anymore!
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-05-20 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 1:23 Kevin Riggle
2008-05-19 23:16 ` William Morgan
2008-05-20 15:03 ` Marcus Williams
2008-05-20 16:05 ` William Morgan [this message]
2008-05-20 16:23 ` Ben Walton
2008-05-25 2:45 ` 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=1211299258-sup-2226@south \
--to=wmorgan-sup@masanjin.net \
/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