factory_bot_rails | factory_bot_rails | Application Framework library

I'm not really sure what happened and why but I tried doing this on my rails container and I was no longer receiving the said error.

1. docker-compose run --rm bash
2. cd to project directory
3. bundle install

You have spring in your gemfile, usually hanging consoles and servers are related to that. The webrick gem was removed from the standard library in Ruby 3, so that's why it needs to be included in your Gemfile.

Re-add webrick to your Gemfile, do a bundle install, and then stop the background spring server with bin/spring stop. Then re-run the server.

Your best bet on solving issues with spring would be to head over and read about the gem on the GitHub project page, or opening a new question here on SO.

According to this issue on github,

You might want to add this to your spec_helper.rb:

Update:

It looks like it was a problem with my post-Bower configuration (I migrated from Bower --> Yarn) I was able to solve Sprockets errors by adding this line to my assets.rb:

Rails.application.config.assets.paths << Rails.root.join('node_modules')

and by running yarn add for files that Sprockets could not locate.

I also made the following updates to old package names in my `application.rb'

To update a object using Factory bot you need to use create in factories. Example:

You should require 'rails_helper' in your rspec tests, not spec_helper.

rails_helper will set up the rails environment for rspec and load spec_helper, but spec_helper does not load rails_helper. Without rails_helper, rspec does not know how to load the Rails code.

How I solved it:

1. Go to server command line
2. As we can see in error log, the last command before error appears was:

Command: cd /home/deploy/project/releases/20201018151933 && ( export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check )

So we go to our folder:

cd /home/deploy/project/releases/20201018151933

and run there command:

export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check

After that we see same error:

Could not find concurrent-ruby-1.1.7 in any of the sources. Run 'bundle install' to install missing gems.

1. In same folder run bundle install and after gem installed we can out of server command line.
2. Run cap production deploy and everything is gonna be fine.

I still don't know what is the root problem of this error, and how to fix it permanently, but this works for me. I hope it will be useful for anyone else.

you should try not do add to lib/generators/factory_bot/model/model_generator.rb

file but you should create custom factories at lib/templates/factory_bot/model/factories.erb

That error message is pretty straight forward. You can't use the transaction strategy on mongoid. That config is for ActiveRecord.

The whole idea of between switching strategies was that transactions are much faster then truncating. But you could not rely on transactions to properly purge the database when running tests that where asynchronous.

Of course that not an option on Mongoid, and Database Cleaner is no longer even relevant on ActiveRecord.