Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Exception
Date: Mon, 27 Jul 2009 09:41:05 -0700	[thread overview]
Message-ID: <1248712764-sup-736@entry> (raw)
In-Reply-To: <1248453259-sup-3604@nixos>

Reformatted excerpts from Marc Weber's message of 2009-07-24:
> Hi, when either running sup-sync or sup (without -n) I get this
> exception:
> 
> --- NoMethodError from thread: poll after loading inbox
> undefined method `to_indexable_s' for nil:NilClass

Weird. It looks like a date parsing issue, but I'm having a hard time
seeing where the logic fails such that no date field is set.

Can you try applying the following patch, and then running sup-sync with
-v? I'm hoping that the debugging output prefixed with XX will provide a
clue.

Thanks!

--- a/lib/sup/message.rb
+++ b/lib/sup/message.rb
@@ -92,11 +92,14 @@ class Message
       begin
         Time.parse date
       rescue ArgumentError => e
-        #Redwood::log "faking mangled date header for #{@id} (orig #{header['da
+        Redwood::log "faking mangled date header for #{@id} (orig #{header['dat
         Time.now
       end
-    else
-      #Redwood::log "faking non-existent date header for #{@id}"
+    end
+
+    @date ||= begin
+      Redwood::log "XX original header was #{header["date"].inspect}"
+      Redwood::log "XX faking non-existent date header for #{@id}"
       Time.now
     end

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2009-07-27 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 16:35 Marc Weber
2009-07-27 16:41 ` William Morgan [this message]
2009-07-27 16:55   ` Marc Weber
  -- strict thread matches above, loose matches on Subject: below --
2010-09-11 16:58 [sup-talk] exception Daniel Goldin
2009-04-26  0:47 [sup-talk] Exception Edward Z. Yang

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=1248712764-sup-736@entry \
    --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