did_you_mean | The gem that has been saving people from typos | Data Manipulation library

In my case, I just did gem install nokogiri and it is working here.

Perhaps the context/env your daemon script gets is different than running locally, though I'm surprised irb gives the same issue in that case.

This is not an official solution. I'm sure the rbenv devs are working on an actual solution but this workaround should help others who are setting up their ruby environments on the new M1 chips for Mac.

• Make sure your Terminal is using Rosetta. You can find how to do that using Google.

• Uninstall your current rbenv following these instructions Removing rbenv. Be sure you also remove all the downloaded versions of ruby if you have any (minus the system default) located in /Users//.rbenv/versions/.

• Uninstall the ARM version of Homebrew with: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall.sh)"

• Install the x86_64 version of Homebrew with: arch -x86_64 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"

• If you run brew install rbenv should produce output saying "Error: Cannot install in Homebrew on ARM processor in Intel default prefix (/usr/local)!". This is expected.

• You want to tell brew to install the older architecture x86_64 arch -x86_64 brew install rbenv

• Then finally install the version you want using arch -x86_64 rbenv install x.x.x (x = some number i.e. 2.7.2)

From there you just need to remember to tell brew arch -x86_64 when installing other versions of Ruby.

Once an actual fix comes through you'll be able to switch back to the newer architecture and not have to use the arch argument. You also don't have to do this all the time with brew either, just rbenv.

This is a RubyMine bug. Nothing we can fix on the Cucumber end.

You can either consult a non-recommended monkeypatch / hack. Or downgrade to an early version of Cucumber5.

See https://youtrack.jetbrains.com/issue/RUBY-27294 for more information, including other possible workarounds and a time-frame for the fix from Jetbrains.

Luke - Cucumber Ruby committer.

Rubygems overwrites Ruby's own Kernel#require method with its own method which loads gems on demand (i.e. adds the gem to the $LOAD_PATH and then requires the requested file).

Thus, when you execute require 'bundler/gem_tasks', what happens is that rubygems searches for a gem containing bundler/gem_tasks.rb in its require_paths path (which is specified in the respective gemspec of each gem). If a matching gem is found on your system, its require_paths are added to the $LOAD_PATH and Ruby's original require method is called which will load the requested file.

In any case, neither Ruby nor Rubygems dynamically loads gems from the internet. It will only use gems installed locally to the configured GEM_PATHS. You can find the configured paths which are searched for installed gems by running gem env on your command line.

If you start Ruby with the --disable-gems command line argument, it will not automatically load rubygems and thus will not add its custom implementation of Kernel#require. Here, only files in locations you specifically added to the $LOAD_PATH can be required.

There may be one culprit gem here but you will run into this problem again and again unless you fix your underlying approach.

Look at your gems environment; all gems are installed into one folder, regardless of the project you’re working on. So, if you have two projects with conflicting dependencies you will get this problem again.

There are tools, like RVM, which let you create environments for each project. So, each project has its own separate collection of gems and even distinct versions of Ruby if you need 2.7 in one project and 2.5 for another.

See "Easy way to setting Ruby Version Manager (RVM) on projects" for how to use RVM and create a gemset for each project.

I think I see what's going on. In your Dockerfile, change your DB_URL from: mysql:// to mysql2://

You are loading the mysql2 gem, but indicating to ActiveRecord that you want to use a connection via the mysql gem.

Credit for this answer goes to Jimmy Cuadra

The Lita handler you showed defines a route that will invoke an instance method called greeting_response when an incoming message matches. There is no instance method with that name defined, hence the "undefined method" exception. You have a method with this name defined in the other file, but a method defined at the top-level scope is not the same thing as an instance method in a class. If you want that method to be included in the Lita handler class, you should define it in a module that you include in the handler.

I tried everything and came to conclusion that there is problem with the binary of ruby 2.3.8 RVM has. The I removed RVM from my system and start using rbenv.

Rather than using /usr/bin/ruby which is the system installed Ruby, use the hashbang