Handle disabling timeouts in indirect ActiveRecord::Migration subclasses #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempts to disable timeouts in non-direct subclasses of
ActiveRecord::Migration
fail in Rails 4.x with the following exception:This was fixed in Rails 5.0 with rails/rails@f37d92c. This PR works around the issue in Rails 4.x by explicitly defining the
ActiveRecord::Migration.say
method which avoids the Rails bug inActiveRecord::Migration.method_missing
. The implementation ofsay
was copied directly from Rails (with some rubocop fixes applied).