[production][notices#create] Mongoid::Errors::InvalidType: Field was defined as a(n) Array, but received a Hash with the value... about errbit HOT 6 CLOSED

The problem is with notifier.js not sending the backtrace as an array.

from errbit.

I'm getting this problem on Heroku when doing GET /apps/new. app/controllers/apps_controller.rb:42:in `new'.

from errbit.

I cannot reproduce this, sorry. If you have updated recently, you may need to run heroku run rake db:migrate

from errbit.

Hmmm. This is weird. I already did, but here goes again (and again).

➜ errbit git:(master) heroku run rake db:migrate
Running rake db:migrate attached to terminal... up, run.1

Mongoid config not found. Create a config file at: config/mongoid.yml
to generate one run: rails generate mongoid:config

Migrating to MoveNoticesToSeparateCollection (20110422152027)
Migrating to MoveIssueTrackersToSti (20110812135951)
Migrating to LinkErrsToProblems (20110905134638)
Migrating to AddProblemCommentsCount (20111019163257)
Migrating to CacheProblemStatisticsFix (20111102173347)
➜ errbit git:(master) heroku run rake db:migrate
Running rake db:migrate attached to terminal... up, run.1

Mongoid config not found. Create a config file at: config/mongoid.yml
to generate one run: rails generate mongoid:config

Migrating to MoveNoticesToSeparateCollection (20110422152027)
Migrating to MoveIssueTrackersToSti (20110812135951)
Migrating to LinkErrsToProblems (20110905134638)
Migrating to AddProblemCommentsCount (20111019163257)
Migrating to CacheProblemStatisticsFix (20111102173347)

Regarding the mongoid config error, I assumed that was not required on heroku?

from errbit.

Hmm. I think something changed on Heroku, in the last few months. I've added an example MongoHQ config, and instructions to the README. Please update, then run the following commands to set up the config file, and then push to heroku and try again. Hope that helps

cp -f config/mongoid.mongohq.yml config/mongoid.yml
git add -f config/mongoid.yml
git commit -m "Added mongoid config for MongoHQ"

from errbit.

Thanks for that. This removes the warning. But I still get the same error. Also migrations are always executed as per example above. I have never used MongoDB before. Is this the way migrations are done on MongoDB?

from errbit.