From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Invalid encoding symbol when doing Marshal.load
Date: Thu, 02 Jun 2011 16:36:04 +0200 [thread overview]
Message-ID: <1307025076-sup-2874@qwerzila> (raw)
Hi,
I've been searching a bit through some old mail and suddenly encountered
the following error:
--- EncodingError from thread: load threads for thread-index-mode
invalid encoding symbol
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:796:in `load'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:796:in `entry'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:571:in `get_entry'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:200:in `block in build_message'
/usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:579:in `synchronize'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:200:in `build_message'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:155:in `block (2 levels) in each_id_by_date'
/home/gaute/dev/ruby/sup.git/lib/sup/thread.rb:338:in `call'
/home/gaute/dev/ruby/sup.git/lib/sup/thread.rb:338:in `block in load_n_threads'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:155:in `block in each_id_by_date'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:250:in `block in each_id'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:250:in `each'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:250:in `each_id'
/home/gaute/dev/ruby/sup.git/lib/sup/index.rb:155:in `each_id_by_date'
/home/gaute/dev/ruby/sup.git/lib/sup/thread.rb:334:in `load_n_threads'
/home/gaute/dev/ruby/sup.git/lib/sup/modes/thread-index-mode.rb:643:in `load_n_threads'
(eval):12:in `load_n_threads'
/home/gaute/dev/ruby/sup.git/lib/sup/modes/thread-index-mode.rb:627:in `block in load_n_threads_background'
/home/gaute/dev/ruby/sup.git/lib/sup.rb:78:in `block in reporting_thread'
running latest 'next'. I've tried to experiment a bit with it, but
haven't found a solution. Trying to encode data, or force_encode the
data to UTF-8.
This happens when listing some old mail, so it could possibly be an
issue with data not _stored_ correctly in the first place.
I still haven't figured out a way to handle the exception and still get
the message structure de-serialized. Any suggestions?
Best regards,
Gaute
next reply other threads:[~2011-06-02 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 14:36 Gaute Hope [this message]
2011-06-09 11:28 ` Gaute Hope
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=1307025076-sup-2874@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@rubyforge.org \
/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