spring-watcher-listen | gem makes Spring watch the filesystem for changes | Runtime Evironment library

Update: To fix this issue I used the solution from @mahatmanich listed here https://stackoverflow.com/questions/31857365/rails-generate-commands-hang-when-trying-to-create-a-model'

Essentially, we need to delete the bin directory and then re-create it using rake app:update:bin

Since rails 5 some 'rake' commands are encapsulated within the 'rails' command. However when one deletes 'bin/' directory one is also removeing the 'rails' command itself, thus one needs to go back to 'rake' for the reset since 'rails' is not available any longer but 'rake' still is.

javascript_pack_tag will render a JavaScript file located in app/javascript/packs/ (Webpacker). In order to render a file in app/assets/javascripts/ (Sprockets), you'll need to use javascript_include_tag.

Alternatively, you could install Bootstrap via Webpacker. Instructions for doing this will vary depending on which version of Bootstrap you'd like to use, but here's a guide on installing Bootstrap 5 via Webpacker.

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

Your error is in the last line;

/var/www/swan/code/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require': cannot load such file -- listen (LoadError)

bundle install --deployment --without development test command install only production and general gems. Does not install the development or test gems. Rails read environment variables RAILS_ENV for the setting environment. RAILS_ENV variable if not set rails default accept development. And bundler try to load all gems + development group gems. But bundle install --deployment --without development test command only install production and general gems. So listen gem is not installed because listen gem in development group. RAILS_ENV=production bin/rails c command not throw error because not try to load development gems.

From your ruby -v, I see that you are in an Intel x86 Mac, but the gem that your trying to build (nokogiri-1.11.3-arm64-darwin) is for new Mac ARM M1 chips. If this is the cause, it means your are using precompiled gems.

Try uninstalling the gem, specify that you don't want to use precompiled gems, and reinstall.

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.

Default headers can be configured in config/application.rb. Trying moving your code out of ApplicationController and into config/application.rb. That's where you'll have access to the config object.

If you need to set custom headers within the context of a controller, you can use response.headers.

Gemfile.lock is a file generated from Gemfile. As such, instead of trying to merge the two branches, it's simpler and more accurate to generate a new one from its canonical source. This might result in slightly different versions, but these should cause no trouble; any version restrictions should be defined in your Gemfile.

Normally one does not commit generated files, they can change in trivial ways, but Gemfile.lock is a special case where you do want this to be the same for all builds.

Resolve any conflicts in the Gemfile. Regenerate Gemfile.lock. Add it.

for some reason he copied the code and added it himself

This is a good opportunity to explain to them why this is a bad practice when working with a team. It might be easy for them, but it's causing trouble for you. They might need instructing in how to update their work in progress. Or you might need to extract some changes into their own branch and get that merged.