My gateway lost network access (so my machine didn't notice) recently and I got a pile of those messages from cron in my inbox: /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `join': No live threads left. Deadlock? (fatal) from /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `block in initialize' from /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `each' from /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `initialize' from /usr/bin/feed2imap:48:in `new' from /usr/bin/feed2imap:48:in `<main>' Now I don't expect feed2imap to do anything magical when network goes out: failing is fine and expected. But "No live threads left. Deadlock?" is hardly a error message anyone should be expected to understand. I would suggest "unreachable host" or something to that effect. :) Thanks
Hello, thanks for your bug report. Fair enough. This is actually an artifact of an over-complicated code for fetching the feeds in multiple threads, and unfortunately it's not as simple as just providing the correct error message. I want to rewrite that code at some point; you can expect this to be fixed in a future new upstream release, but don't hold your breath. ;-)