less-rails | : -1 : : train : Less.js For Rails | Animation library

Whenever you run a Rails command, it will potentially set up a bunch of classes before doing the actual work, and unlike many other languages, in Ruby this setup is done by actual Ruby code (this is how DSLs work), and any broken code that runs during that time will prevent any commands from running.

It won't run any instance methods, but any broken class-level code will cause issues.

So the migration thing is just a red herring, presumably all your Rails commands are broken.

According to your stacktrace, app/models/user.rb:8 (which you haven't provided), is getting run during initialisation. Models getting loaded during initialisation is quite common, but in this case that code is breaking.

Looking at the ActiveRecord source code (with less -N `bundle show activerecord`/lib/active_record/persistence.rb and looking at line 138), you seem to be calling the destroy class method (e.g. User.destroy(1)) but without parameters, like you do with the destroy instance method (e.g. User.find(1).destroy). So you should make sure you understand the difference between these two.

I'm not sure why you would be calling User.destroy outside of an instance method, but not having the relevant user model code I cannot say. Is there just a stray "destroy" by itself there?