rb-inotify | A thorough inotify wrapper for Ruby using FFI | Wrapper library

This seems like everything is working correctly rails just likes to output what its doing to the console but it should have added those to your file.

What I would suggest is to ensure that your GEM_PATH contains the path that you have set in your GEM_HOME variable. Myself, I have those environment variables which work all the time:

The docs for shopify cli mention that you need ruby 2.7 installed on your system. From looking at your output, you're using ruby 2.6.

https://shopify.dev/apps/tools/cli/installation

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.

The issue was related to environment variables and not being able to find the correct path for the gems. I found a solution and updated the schedule.rb file.

I had the same problem and I found a workaround here at https://github.com/jekyll/jekyll/issues/8523

Add gem "webrick" to the Gemfile in your website. Than run bundle install

At this point you can run bundle exec jekyll serve

For me it works!

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

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.

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.