rvm | Development repository for the rvm cookbook | Infrastructure Automation library

I managed to make it work again by removing RVM completely from my system using the commands in https://rvm.io/support/troubleshooting.

i ended up upgrading wsl to wsl 2 using wsl --set-version Ubuntu-18.04 2 from a powershell terminal

i had to delete the corrupted ruby files for this to work but the first run gave me the location of the files. and a couple of rm -rf allowed the process to complete.

Be warned this is a relatively long process took me approx 15mins per run.

after the process i was able to run the install of ruby 3.0.0 with no problem.

thank you NotTheDr01ds for putting me on track with a solution

According to this documentation:

When supplying hashes for request objects. If it is the last argument to a method, some versions of Ruby will interpret the hash as keyword arguments. To prevent this, appending an empty hash as an extra parameter will avoid misinterpretation.

I was blocked by the same thing for a week. Finally finding this Reddit thread, which seems like the simplest explanation so far: https://www.reddit.com/r/GnuPG/comments/o5tb6a/keyservers_are_gone/ ...switching to keys.openpgp.org finally worked for me.

I had googled a lot and nothing at the top results worked. I tried the different hostnames, adding :80 port specification, prefixing 0x on the key signatures, and so on. Today I finally found that thread.

It turns out the problem was that in the Gemfile.lock file, it was locked to using an older version of bundler. We simply deleted the Gemfile.lock, and re-ran bundle to regenerate Gemfile.lock. That solved it. It now says this at the bottom of the Gemfile.lock file, so it liked this version of bundler:

I'll bet your RVM isn't set up correctly and /usr/bin/ appears in your PATH before RVM's bin directory. Run echo $PATH to confirm.

If so, back up your dotfiles for safety and run rvm get head --auto and it should put your PATH right. Logout and log back in or source your dotfiles (source ~/.bash_profile or whatever) and try again.

I was able to install successfully on Mac Big Sur with my Rails 6.1.4, Ruby 3 project with these gems ...

You need to include Active Model Serialization wherever you're initializing the serializer.

For instance, in your /application_controller.rb:

The n message is telling you that the version it just "installed" and the version that is "active" are different. You have two versions of node installed, and the active version is the one that is first in the PATH.

The active version is /usr/local/opt/node@14/bin/node. I don't recognise that path, not sure what was used to install that. It must be in your PATH variable and there might be a clue in your login script as to what added /usr/local/opt/node@14/bin to the PATH?

To get the n installed version of node to be the active version, you could delete the other copy of node, or put /usr/local/bin earlier in PATH so it is found first, or simplest remove /usr/local/opt/node@14/bin from your PATH variable.