-
Notifications
You must be signed in to change notification settings - Fork 83
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
After trigger event #10
Comments
@pragmaticivan is there a stack trace that leads you to this gem causing it? |
@rosskevin - It looks like a change that might have to be made in the gem. Paper Trail had the same issue: paper-trail-gem/paper_trail#416 |
It looks like this is confirmed to be unrelated to state_machines. Even though state_machines will be somewhere in the call stack, it seems to be other gems or an AR related issue. Agreed? |
@pragmaticivan Might you be using activerecord-import? I got the same warning after upgrading to the state-machines gem, which led me here. But the warning indicated a line where I was using activerecord-import. I upgraded activerecord-import and the warning is gone. activerecord import does use Obviously it could be some other gem. It's possible after updating to state_machines, code that was not previously running started to work again which is calling the other library. |
I'm getting this warning after trigger an state machine event:
The text was updated successfully, but these errors were encountered: