Ruby Autoload Conflicts Between Gmail and Parse_Resource Gems

Ruby autoload conflicts between gmail and parse_resource gems

I had installed the gems with bundler.

To fix the issue with loading both libraries, I installed the gems with the gem command:
sudo gem install gmail parse_resource

With this done, I was able to require the libraries in any order, and to connect to gmail and parse without issue.

-Nick

Only one version of Ruby works when multiple versions are installed

I had the exact same issue, except using rbenv with bash.

The perpetrator seems to be the echo "export RUBYOPT='-W:no-deprecated -W:no-experimental'" line in your .zsh file, I'm not sure if Ruby 2.6.5 understands it.

Remove echo "export RUBYOPT='-W:no-deprecated -W:no-experimental'" from your .zsh / .bashrc / .profile and restart your shell.

Ruby On rails : need to run /bin/bash before any rails command

This looks like a path issue to me. When you run rails the first time, it's finding a global rubygems installation before your local rvm copy.

After you run /bin/bash from the command line, you are starting an interactive shell, which sources (executes) ~/.bashrc. My guess is that that contains the rvm initializations that are failing to run when you login with a login shell.

Take a look at ~/.bash_profile and ~/.bashrc. Here is what the latest RVM installer generates:

$ cat ~/.bashrc
PATH=$PATH:$HOME/.rvm/bin # Add RVM to PATH for scripting

$ cat ~/.bash_login 
[[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm" # Load RVM into a shell session *as a function*
export NODE_PATH=/usr/local/lib/node_modules
if [ -f ~/.bashrc ]; then
   source ~/.bashrc
fi

If this is what you've got, then you're somehow logging in through an interactive shell and not a login shell (how???). You should be able to fix both issues with source ~/.bash_profile (.bash_login in OS X).

Using jekyll with gitlab pages, it says when it's deploying the website with gitlab CI that theme could not be found, and I already installed it

In your Gemfile, uncomment #gem "jekyll-theme-basically-basic" to read gem "jekyll-theme-basically-basic".

For some reasons, in your .gitlab-ci.yml, all the gem install ... are useless, and it's the bundle install that does the required job.

---

Related Topics