Fix for attr_accessor_with_default causing "singleton can't be dumped" exception on marshaling #1088
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…TypeError on object marshaling [rails#4776 state:resolved]
|
Thanks bro but I am deprecating attr_accssor_with_default because it is just much easier for you to implement the method yourself instead. |
|
Thanks for the prompt response. Yes, doing such thing by hand makes sense. The bug is in there until old implementation is present though. |
jake3030
pushed a commit
to jake3030/rails
that referenced
this pull request
Jun 28, 2011
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please find proposed fix for attr_accessor_with_default. It addresses the problem which can be triggered by memcached client library when it tries to marshal an object with non-default attribute value. #refactotum