-
-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stack Level Too Deep on YAML Serialization #385
Comments
I have a workaround for now with |
Hmm. I don't think the YAML serialization should be particularly impactful. The point you call out for recursion is related to reading back files from s3, rather than uploading them, which also makes me less sure about how this interaction is happening. Does the paper_trail call you make there just NOT upload the image? Sorry I'm not able to be more directly helpful, but it may make more sense for you to ask on the papertrail repo as it's not clear to me this is a bug in fog. Does that make sense? |
I have encountered the same problem. This is the repeating part of the stack trace:
|
It seems to be connected with this issue - paper-trail-gem/paper_trail#134 |
Thanks for the additional detail. It sounds more like an issue with how paper_trail tries to serialize the uploader than an issue with the uploader itself. As such, it would probably make sense to report it over there instead. That said, in the linked issue it suggests a |
PaperTrail is serializing the uploaded file (using CarrierWave) to YAML when the record is updated and the result is an infinite loop. Specifically,
fog-aws
is causing a crash when it iterates through files:This recurses until Ruby crashes on the stack level too deep error.
If it matters, the Ruby version is 2.4.1. There should only be one image file associated with the model that Paper Trail is saving a version of.
fog-aws
version: 1.4.0paper_trail
version: 7.1.0The text was updated successfully, but these errors were encountered: