From scs@geneseecounty911.org Thu Dec 1 08:54:10 2011 From: scs@geneseecounty911.org (Scott Shook) Date: Thu, 01 Dec 2011 08:54:10 -0500 Subject: [sup-talk] maildir with spaces In-Reply-To: <20111201004855.GQ899@tracyreed.org> References: <20111130221624.GM899@tracyreed.org> <20111201004855.GQ899@tracyreed.org> Message-ID: <1322747029-sup-96@rambo.gcc.local> I had this same problem and I ended up creating symlinks without a space in the name. Keep the offlineimap config the same but change sup source to the symlink'd folder. I.E. > maildir:///home/treed/Maildir/mydomain/Sent Mail (URI::InvalidURIError) ln -s /home/treed/Maildir/mydomain/Sent\ Mail /home/treed/Maildir/mydomain/Sent Scott From treed@ultraviolet.org Thu Dec 1 13:02:48 2011 From: treed@ultraviolet.org (Tracy Reed) Date: Thu, 1 Dec 2011 10:02:48 -0800 Subject: [sup-talk] before-pull hook etc. In-Reply-To: <20111130221624.GM899@tracyreed.org> References: <20111130221624.GM899@tracyreed.org> Message-ID: <20111201180247.GS899@tracyreed.org> On Wed, Nov 30, 2011 at 02:16:24PM -0800, Tracy Reed spake thusly: > accept my sincere apologies. Please submit the contents of > /home/treed/.sup/exception-log.txt and a brief report of the > circumstances to http://masanjin.net/sup-bugs/ so that I might > address this problem. Thank you! I forgot to mention: I tried to submit these to the bug tracker mentioned in the stack trace but the url 404's. I just realized perhaps I should be submitting this stuff to sup-devel so I will subscribe there and will post some of these questions and the stack traces over there. -- Tracy Reed -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From john.wyzer@gmx.de Mon Dec 5 12:45:24 2011 From: john.wyzer@gmx.de (John Wyzer) Date: Mon, 05 Dec 2011 18:45:24 +0100 Subject: [sup-talk] reproducable crashing / encoding problem Message-ID: <1323106615-sup-792@localhost> I'm on sup/mainline:master (commit aaa852fbe513291144301bb31af50558177f891c) Opening one specific thread, sup always crashes with the attached trace. Best regards! :-) ---------------------------------------------------------------- --- Encoding::CompatibilityError from thread: load messages for thread-view-mode incompatible character encodings: UTF-8 and ASCII-8BIT /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:789:in `message_patina_lines' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:863:in `chunk_to_lines' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:721:in `block in regen_text' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:68:in `block in each' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:176:in `block (2 levels) in each_with_stuff' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:176:in `block (2 levels) in each_with_stuff' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:174:in `each_with_stuff' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:176:in `block in each_with_stuff' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:175:in `each' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:175:in `each_with_stuff' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:176:in `block in each_with_stuff' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:175:in `each' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:175:in `each_with_stuff' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:67:in `each' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:710:in `regen_text' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:172:in `buffer=' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/buffer.rb:388:in `spawn' (eval):1:in `spawn' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-index-mode.rb:120:in `block in select' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup.rb:79:in `block in reporting_thread' From jomat+sup-talk@jmt.gr Mon Dec 5 14:36:28 2011 From: jomat+sup-talk@jmt.gr (jomat+sup-talk at jmt.gr) Date: Mon, 05 Dec 2011 19:36:28 +0000 Subject: [sup-talk] reproducable crashing / encoding problem In-Reply-To: <1323106615-sup-792@localhost> References: <1323106615-sup-792@localhost> Message-ID: <1323113200-sup-9566@v2.zyria.de> Excerpts from John Wyzer's message of 2011-12-05 17:45:24 +0000: > I'm on sup/mainline:master (commit aaa852fbe513291144301bb31af50558177f891c) Same here: aaa852fbe513291144301bb31af50558177f891c > Opening one specific thread, sup always crashes with the attached trace. > Best regards! :-) > > ---------------------------------------------------------------- > --- Encoding::CompatibilityError from thread: load messages for thread-view-mode > incompatible character encodings: UTF-8 and ASCII-8BIT > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:789:in `message_patina_lines' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:863:in `chunk_to_lines' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:721:in `block in regen_text' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:68:in `block in each' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:176:in `block (2 levels) in each_with_stuff' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:176:in `block (2 levels) in each_with_stuff' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:174:in `each_with_stuff' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:176:in `block in each_with_stuff' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:175:in `each' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:175:in `each_with_stuff' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:176:in `block in each_with_stuff' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:175:in `each' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:175:in `each_with_stuff' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/thread.rb:67:in `each' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:710:in `regen_text' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-view-mode.rb:172:in `buffer=' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/buffer.rb:388:in `spawn' > (eval):1:in `spawn' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-index-mode.rb:120:in `block in select' > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup.rb:79:in `block in reporting_thread' Could be related to a problem I recently encountered when forwarding a specific message. Upon pressing 'y' to send it, sup does this: [2011-12-05 19:21:16 +0000] ERROR: oh crap, an exception ---------------------------------------------------------------- I'm very sorry. It seems that an error occurred in Sup. Please accept my sincere apologies. Please submit the contents of /home/jomat/.sup/exception-log.txt and a brief report of the circumstances to http://masanjin.net/sup-bugs/ so that I might address this problem. Thank you! Sincerely, William ---------------------------------------------------------------- --- Encoding::CompatibilityError from thread: main incompatible character encodings: UTF-8 and ASCII-8BIT /var/lib/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:112:in `serialize_low' /var/lib/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:99:in `block in serialize_low' /var/lib/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/message.rb:155:in `block in each_part' /var/lib/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/message.rb:154:in `each' /var/lib/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/message.rb:154:in `each_part' /var/lib/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:96:in `serialize_low' /var/lib/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:63:in `serialize' /var/lib/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/message.rb:146:in `to_s' /home/jomat/sup/lib/sup/modes/edit-message-mode.rb:455:in `puts' /home/jomat/sup/lib/sup/modes/edit-message-mode.rb:455:in `block in send_message' /home/jomat/sup/lib/sup/modes/edit-message-mode.rb:455:in `popen' /home/jomat/sup/lib/sup/modes/edit-message-mode.rb:455:in `send_message' /home/jomat/sup/lib/sup/mode.rb:59:in `handle_input' /home/jomat/sup/lib/sup/buffer.rb:278:in `handle_input' ./bin/sup:271:in `' ./bin/sup:80:in `
Didn't find time yet to remove the sensible stuff of the message to attach it to the report, but it contains umlauts. cu, jomat From jason.oconal@ieee.org Fri Dec 9 22:08:30 2011 From: jason.oconal@ieee.org (Jason O'Conal) Date: Sat, 10 Dec 2011 13:38:30 +1030 Subject: [sup-talk] (no subject) Message-ID: Hi, I've been having trouble getting sup to work with my gmail account downloaded by offlineimap. I have set up everything according to the tutorial available at http://sup.rubyforge.org/wiki/wiki.pl?GmailOfflineImapSmtp I can't get sup-sync to run. I get the following error message: /usr/lib/ruby/1.8/yaml.rb:133:in `transfer': invalid subclass (TypeError) from /usr/lib/ruby/1.8/yaml.rb:133:in `node_import' from /usr/lib/ruby/1.8/yaml.rb:133:in `load' from /usr/lib/ruby/1.8/yaml.rb:133:in `load' from /usr/lib/ruby/1.8/yaml.rb:144:in `load_file' from /usr/lib/ruby/1.8/yaml.rb:143:in `open' from /usr/lib/ruby/1.8/yaml.rb:143:in `load_file' from /usr/lib64/ruby/gems/1.8/gems/sup-0.12.1/lib/sup.rb:136:in `load_yaml_obj' from /usr/lib64/ruby/gems/1.8/gems/sup-0.12.1/lib/sup.rb:266:in `load_config' from /usr/lib64/ruby/gems/1.8/gems/sup-0.12.1/lib/sup.rb:157:in `start' from /usr/lib64/ruby/gems/1.8/gems/sup-0.12.1/bin/sup-sync:80 from /usr/bin/sup-sync:19:in `load' from /usr/bin/sup-sync:19 I have tried to search for others with this error, but can't find anything relevant (tried only using folders without spaces to no avail). Any ideas? Kind regards, Jason O'Conal From dmishd@gmail.com Sat Dec 17 13:47:29 2011 From: dmishd@gmail.com (Hamish D) Date: Sat, 17 Dec 2011 18:47:29 +0000 Subject: [sup-talk] exception --- RuntimeError from thread: poll after loading inbox In-Reply-To: <1320868149-sup-368@qwerzila> References: <56777.143.205.193.62.1320657425.squirrel@lavabit.com> <1320700740-sup-9219@tilus.net> <1929.143.205.216.123.1320746264.squirrel@lavabit.com> <1320868149-sup-368@qwerzila> Message-ID: >> bin/sup-sync:11: warning: method redefined; discarding old to_s >> /home/gaute/dev/ruby/sup.git/lib/sup.rb:18:in `id': wrong id called on > > This seems to be due to the new yamler 'psych', by requiring the old one > 'sych' before 'yaml' it can be loaded. > > The proper fix is to expect content to be represented the way 'psych' > does it. This is not the same as the old way. > > Also the gem spec date was in the wrong format, see both attached > patches. Both patches applied to next. Hamish From alex.shulgin@gmail.com Fri Dec 23 10:31:08 2011 From: alex.shulgin@gmail.com (Alex Shulgin) Date: Fri, 23 Dec 2011 17:31:08 +0200 Subject: [sup-talk] Sup crashes when loading a message Message-ID: Got this crash today: --- NoMethodError from thread: periodic poll undefined method `downcase' for nil:NilClass /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/rmail-1.0.0/lib/rmail/header.rb:537:in `content_type' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/message.rb:427:in `message_to_chunks' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/message.rb:427:in `map' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/message.rb:427:in `message_to_chunks' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/message.rb:259:in `load_from_source!' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/message.rb:328:in `build_from_source' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:158:in `poll_from' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/mbox.rb:143:in `poll' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:155:in `poll_from' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:113:in `do_poll' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:103:in `each' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:103:in `do_poll' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:102:in `synchronize' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:102:in `do_poll' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/util.rb:609:in `send' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/util.rb:609:in `method_missing' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/modes/poll-mode.rb:15:in `poll' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:49:in `poll_with_sources' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:68:in `poll' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:86:in `start' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup.rb:78:in `reporting_thread' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup.rb:76:in `initialize' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup.rb:76:in `new' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup.rb:76:in `reporting_thread' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/poll.rb:83:in `start' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/util.rb:609:in `send' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/lib/sup/util.rb:609:in `method_missing' /home/ash/.rvm/gems/ruby-1.8.7-p352/gems/sup-0.12.1/bin/sup:222 /home/ash/.rvm/gems/ruby-1.8.7-p352/bin/sup:19:in `load' /home/ash/.rvm/gems/ruby-1.8.7-p352/bin/sup:19 Seems like rmail doesn't really like an empty "Content-Type: " header: rmail/header.rb: def content_type(default = nil) if value = self['content-type'] value.strip.split(/\s*;\s*/)[0].downcase # <== crashes on value="" else if block_given? yield else default end end end Adding (... || "") before downcase seems to help this crash.