Rails.cache.read a small bug?
Reported by stanislav | July 23rd, 2008 @ 05:37 PM | in 2.x
Hi,
I think I hit a strange and minor bug of Rails.cache.read . Well, the problem is that when I call exactly this:
Rails.cache.read("front_page_channels_tags_hash")
I get this Exception:
-------------------
ArgumentError: marshal data too short
from /usr/lib64/ruby/gems/1.8/gems/memcache-client-1.5.0/lib/memcache.rb:214:in `load'
from /usr/lib64/ruby/gems/1.8/gems/memcache-client-1.5.0/lib/memcache.rb:214:in `get'
from /usr/lib64/ruby/gems/1.8/gems/activesupport-2.1.0/lib/active_support/cache/mem_cache_store.rb:26:in `read'
from (irb):56
-----------------
If I change a single word or letter - it's OK. If I remove any world or letter - it's again OK.
I've tested that on Linux and Mac.
memcahe_store - memcached
Rails 2.1.0
It's not imported becouse the simple workaround is just to change the string. However, I'm curious where the problem is.
Stan.
Comments and changes to this ticket
-
stanislav July 23rd, 2008 @ 05:44 PM
Please close it. There is something with my tests that causеs that problem.
-
Pratik July 24th, 2008 @ 10:27 AM
- → State changed from “new” to “invalid”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
