-
Notifications
You must be signed in to change notification settings - Fork 165
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
MongoDB 3.6 --> Mongo::Error::OperationFailure: Unknown modifier: $pushAll #189
Comments
I think this is an issue with the mongoid (v6) gem itself: Thoughts? Edit: It looks like mongoid v7 fixes the problem. Is it possible for you to try to upgrade to that? |
I tried but upgrading to Mongoid v7 requires that I upgrade too many other gems. Currently I'm stuck on mongoid 6.1.1 but I'll be working on the upgrade. I also discovered another problem (which might be fixed with a mongoid upgrade) : It seems like
It seems like the Note that the following works :
I'm not sure if I should open a ticket or wait to see if Mongoid v7 will fix that too |
@Startouf I had the same error and updated Mongoid to 6.4.2 and it went away. Maybe try it out since it's still on the 6.x branch? |
I agree I think it’s healthier moving forward that we close this instead of waiting for a fix to carrierwave
Nik So
… On Nov 6, 2018, at 6:09 PM, Cyril Duchon-Doris ***@***.***> wrote:
@rmm5t I have migrated to Mongo v7 a couple days ago on our production app (it was quite a pain btw) and the error's gone, and it seems like @niksosf also fixed it by bumping Mongoid6, so I guess we can close ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
It seems that the $pushAll operator was removed in MongoDB 3.6, making systematic crashes when trying to update an uploader
My gem/server versions
Here is a full stack trace. At first sight it doesn not seem related to mongoid carrierwave, but the bug only occurs when I try to add an image file so I'm not sure what to think of it
The text was updated successfully, but these errors were encountered: