nokogiri | Nokogiri makes it easy and painless to work with XML | Parser library

You should upgrade nokogiri to the latest possible for your project, especially when dealing with security issues. There are some caveats to this particular advisory, so you might not be vulnerable, but when dealing with security it's better to be overly cautious.

The note on Wikipedia refers to the MRI CRuby implementation as opposed to the others (like jruby).

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.

I had a similar problem with a Rails app that has dependency on Nokogiri running on an Alpine based container on my Macbook M1. Here is what I did:

1. Reading the Nokogiri documentation, I found out that aarch64-linux (the architecture used inside the Docker container) is actually supported, but it requires glibc >= 2.29.

2. I am far from being an expert but, as far as I know, Alpine distributions don't include glibc but musl. Fortunately, there are ways to run programs that need glibc in Alpine.

3. I personally followed the first option, that is, I installed gcompat. I just needed to add gcompat to the list of packages to install in my Dockerfile.

   RUN apk add --no-cache ... gcompat

4. After that change, things went smoothly and the Rails app started up with no issues.

Again, I am not an expert and the above might be inaccurate, but it did the magic for me. I hope it can help you too.

Once you get to the script tag, nokogiri's work is done, and it's time to parse JSON.

When you use w option it always rewrite onto the file. What you need is to create or append to the file, it's done with the a option. So you can try this:

File.open(split_date,'a'){ |f| f << item }

PS. Be sure that split_date as the name of the file is uniq for each node since you want a separate file per node

You are missing a dot . at the beginning of your XPath expression.
Instead of

The URL used in mailers is specified by:
Rails.application.configure.action_mailer.default_url_options

In config/environments/test.rb I had set mine to port 3000 when I first installed Clearance:
config.action_mailer.default_url_options = {host: "localhost:3000"}

To fix it, I first tried specifying the port dynamically but the suggested method didn't actually work and it seems it isn't necessary. Removing the port number was enough to get my system test passing:
config.action_mailer.default_url_options = {host: "localhost"}

As mentioned by Thomas Walpole, the reason this works is that Capybara.always_include_port is set to true. With this setting, attempts to access http://localhost/confirm_email/ (with no port specified) are automatically rerouted to http://localhost:/confirm_email/.

The always_include_port setting defaults to false in the Capybara gem but it turns out Rails sets it to true when it starts up the System Test server.

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.

First of all it'll be great if you shared the Gemfile.lock error so as to know what i particular might be causing that upgrade. But from afar I think as you said this gem is a dependency gem and it is not stated in your gemfile. It could be that another gem also depends on this gem and per that requirement it triggers an upgrade even before your supposed gem line is run which may be leading to the error. Read the error thoroughly and you can identify the gem(s) causing this.

After your update I have read around on this. Exactly so as stated earlier on, one of these gems could be the reason why your particular gem gets updated with every bundler install. Unfortunately there is no true turn around to solving this but bundler does give a way around. You can use the --frozen option with bundler which freezes your gemfile.lock to the current versions for each gem and does not update any gem but only installs new gems that you have. Unfortunately this has been deprecated and can only be done be done from /.bundle/config. This can be done from the command line in the root of your project. run bundle config frozen true to freeze bundler from updating your gems in gemfile.lock You may have to grant write permissions to your user to be able to edit the bundle configurations. I found this article as well from bigbinary.com