Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: manish@gslab.com (Manish Sapariya)
Subject: [sup-talk] exception while syncing
Date: Thu, 01 Nov 2007 10:29:59 +0530	[thread overview]
Message-ID: <47295D4F.9020101@gslab.com> (raw)

Hi All,
Is this known issue? If yes, can anyone suggest workaroud, if no
where can log bug for this issue? Please let me know if you need
more info in any case.

I saw following warnings before the crash.
[Thu Nov 01 10:11:12 +0530 2007] warning: error decoding message body
from "us-ascii": "\222t waste time. C"...
[Thu Nov 01 10:11:12 +0530 2007] ignoring erroneous message at
mbox:/data/personel/mails/ImapMail/INBOX#25586133: no message-id field
in header {} (source mbox:/data/personel/mails/ImapMail/INBOX offset
25586133)
[Thu Nov 01 10:11:56 +0530 2007] warning: error decoding message body
from "iso-8859-8-i": invalid encoding ("UTF-8", ""iso-8859-8-i"")
[Thu Nov 01 10:12:01 +0530 2007] warning: error decoding message body
from "us-ascii": "\222ll save up to 5"...
## 2344 (32.39%) read; 0:01:00 elapsed; 0:02:05 remaining
[Thu Nov 01 10:12:08 +0530 2007] warning: error decoding message body
from "ks_c_5601-1987": invalid encoding ("UTF-8", ""ks_c_5601-1987"")


/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser/multipart.rb:159:in
`[]=': can't modify frozen string (TypeError)
        from
/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser/multipart.rb:159:in
`read_chunk_low'
        from
/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser/multipart.rb:94:in
`loop'
        from
/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser/multipart.rb:94:in
`read_chunk_low'
        from
/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser/multipart.rb:76:in
`read_chunk'
        from
/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser/pushbackreader.rb:85:in 

`read'
        from
/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser.rb:285:in
`parse_singlepart_body'
        from
/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser.rb:198:in
`parse_low'
        from
/usr/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser.rb:275:in
`parse_multipart_body'
         ... 26 levels...
        from /usr/lib/ruby/gems/1.8/gems/sup-0.1/bin/sup-sync:128:in `each'
        from /usr/lib/ruby/gems/1.8/gems/sup-0.1/bin/sup-sync:128
        from /usr/bin/sup-sync:16:in `load'
        from /usr/bin/sup-sync:16

Regards,
Manish



             reply	other threads:[~2007-11-01  4:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01  4:59 Manish Sapariya [this message]
2007-11-01  5:33 ` Colin Bell

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=47295D4F.9020101@gslab.com \
    --to=manish@gslab.com \
    /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