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 <[EMAIL PROTECTED]> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
