You're right. I fixed it today by running sup-sync. (I was still reading
my mails that's why I didn't respond earlier).
I used p m at that location to get a message output saying something
about offset is out of sync. Then I tried sup-sync -c.
The strange thing is that I didn't open the mbox file using another
program such as mutt. Maybe a locking issue or such ? I'm using
procmail.
I was surprised how easy it was to find the cause after starting looking
into it.
Thanks for taking the time sending this patch!
Marc Weber
Excerpts from William Morgan's message of Mon Jul 27 18:41:05 +0200 2009:
> 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
>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
