Conflict with specific ActiveRecord scopes

[adamcreekroad]

There is some weird behavior happening with scopes with the names after and every.

For example if you have a model with a scope called after, it will work fine when called by itself Job.after. BUT if you put any other scope before it Job.active.after then it breaks with the error undefined method 'limit' for #<Thread:0x0000000003a45bc0>.

Tracking that down, it looks as though for some reason it is calling the Kernel#after defined in hyper-operation/delay_and_interval.

This can be replicated on the server in a rails console.

[adamcreekroad]

The solution (not the prettiest, but works)

module Kernel
  def every(time, &block)
    if RUBY_ENGINE != 'opal' && defined?(ActiveRecord::Relation) && is_a?(ActiveRecord::Relation)
      super
    else
      Thread.new { loop { sleep time; block.call } }
    end
  end

  def after(time, &block)
    if RUBY_ENGINE != 'opal' && defined?(ActiveRecord::Relation) && is_a?(ActiveRecord::Relation)
      super
    else
      Thread.new { sleep time; block.call }
    end
  end
end

ActiveRecord's magic uses method missing to call the scope defined in the model on the ActiveRecord::Relation, but since Kernel defines those methods it never gets there. So there's really no nice way around it.