Skip to content
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

The @object is not compatible with ActiveJob #2847

Closed
meinac opened this issue Mar 9, 2017 · 3 comments
Closed

The @object is not compatible with ActiveJob #2847

meinac opened this issue Mar 9, 2017 · 3 comments
Milestone

Comments

@meinac
Copy link

meinac commented Mar 9, 2017

The @object variable which instantiated by RailsAdmin is not compatible with ActiveJo, means If you try to send this object to a backend job via ActiveJob' perform_later API it raises an exception which says Unsupported argument type: Foo. This error may lead someone to wrong direction because the class is not Foo, actually its type is RailsAdmin::Adapters::ActiveRecord::AbstractObject which delegates almost its all methods to ActiveRecord object.

I know this is by design but I've spent lots of time to figure it out and it's really hard to understand what is the problem because of this design, you may want to consider this as should be fixed or documented for future incidents.

@shunwen
Copy link

shunwen commented Oct 3, 2018

Still having this issue.

@pokonski
Copy link

Same issue. RailsAdmin does something that results in ActiveRecord objects not being able to be serialized.

@sbull
Copy link
Contributor

sbull commented Oct 29, 2020

More complete error message for easier Google hits:
ActiveJob::SerializationError (Unsupported argument type: <@object.class>):

@mshibuya mshibuya added this to the 3.0.0 milestone Oct 8, 2021
@mshibuya mshibuya removed the cleanup label Oct 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants