rack-test | Rack : :Test is a small , simple testing API for Rack apps | HTTP library

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 think you need a webpacker.yml file in your apps config file. I also suggest running bundle install and bundle update commands before launching the rails server after you installed a gem. Here's a closed issue similar to your problem; https://github.com/rails/webpacker/issues/940

ModuleNotFoundError: Module not found: Error: Can't resolve '@popperjs/core' suggests that you need to install @popperjs/core.

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

The main problem here is that the command mkdir is being called at a specific location, and it's just not there:

make: /usr/bin/mkdir: Command not found

To fix this, you need to add a symbolic link to that location:

$ sudo ln -s /bin/mkdir /usr/bin/mkdir

Run gem install again on rails and all should be good!

Thanks to user dem1tris from brining up a related topic, and providing the answer: make: /usr/bin/mkdir: Command not found during `gem install nokogiri` in Ubuntu 20.04

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.

As with all open source software, you have a few options:

1. Keep using the old software version (i.e. don't use ruby v3.0.0).
2. Hope that someone else updates the dependencies for you.
3. Do the update yourself.
4. Stop using the library.

At the moment, option 1 is totally viable; ruby 2.7 is still actively maintained, and support will probably continue until 2023-03-31. You could do this, simply hoping that option 2 becomes available soon.

The standard practice for option 3 is:

• Fork the project, and make the fixes.
• Open a pull request to the main repo with your fixes. Hopefully it gets merged.
• In the meantime, if you need to be unblocked, reference your forked repo in other projects.

This is clearly more effort, but I wouldn't call it a "yuck" solution; not unless your changes are drastic/introduce compatibility issues with the main project, and the two branches diverge.

As for option 4, as with virtually any library replacement, there's always going to be some trade-off between compatibility/features, but clearly other testing frameworks do exist. It depends how you are actually using it. Your mileage may vary.

In summary, I can't really give an objective answer to such a subjective question, but my advice at the moment would be: If you have time/skill/motivation to update to ruby 3 right now, then fork the dependency and update it. (It's probably not a massive change needed!).

But if you lack the time/skill/motivation to do this, then just stick with ruby 2.7 for now.

I had set the configuration livy.master to local, when i removed this configuration everything worked properly.

Try specifying your ActiveRecord to version 5.2 on your Gemfile, since you're using that Ruby version. Also, make sure you include it on your generated migrations.

So on your case: