NoMethodError: undefined method `perform' for nil:NilClass about strong_migrations HOT 9 CLOSED

Migrations inherit from ActiveRecord::Schema, which can run operations without methods. Anyways, I updated the code to be more robust to this scenario.

from strong_migrations.

Hey @ziaulrehman40, Strong Migrations is tested against Rails 5.1 (https://travis-ci.org/ankane/strong_migrations), so think something else in your app may be interfering with it.

from strong_migrations.

@checker should be set on initialization, but maybe another gem is overriding it?

from strong_migrations.

It was working fine on 4.2 and 5.0, i can check what else ot updated while migrating on 5.1.

Though nothing really stands out, but I updated haml-rails, pg and added listen gem.

Nothing else i can in my changelog. I can try reverting these gem updates/additions if that helps.

from strong_migrations.

No, didn't help. I undid all gemfile changes and still same.

from strong_migrations.

The error doesn't occur in the test suite or a fresh Rails 5.1 app, so all signs point to something in your app.

from strong_migrations.

Yeah i understand that, but we must hunt it down whatever it is.
I will try to spend some time on this and as soon as I find something i will report.

Just to add,

1. StrongMigrations.start_after is set, and there are a few migrations that run just fine after this set timestamp value, and this specific one fails which is near end of the list(second last).

2. If i comment this specific migration's actual migration stuff, it passes over it just fine.

from strong_migrations.

Oh found it...

If you look closely, you can see there is no def change or def up in the migration i have pasted above, that was the issue. wrapping migration in a def change fixed it.

I am not sure how it was even working in older versions... this is confusing.

from strong_migrations.

Thankyou @ankane , this approach was what came to my mind when i was investigating, but you were super fast to push a commit. 👍

from strong_migrations.