Shopify CLI not recognising correct ruby install - ruby

When logging into a store with Shopify CLI I am given the following error:
"Your environment Ruby version, 2.6.3, is outside of the range supported by the CLI, 2.6.6..<3.2.0, and might cause incompatibility issues."
I am getting a general 'unexpected' error on a range of commands and believe it's due to the issue above. Thing is, I have latest ruby installed via homebrew, so it seems Shopify CLI is seeing another install.
I have tried reinstalling shopify-cli through homebrew using
brew reinstall shopify-cli
But this doesn't help.
If I run
ruby -v
I get the version mentioned in the error which shopify cli is seeing: "ruby 2.6.3p62 (2019-04-16 revision 67580) [universal.arm64e-darwin21]"

Not sure if you fixed this, but I figured it out using this tool. Run brew config command, and look for the CLT: key: If it says >14.x, then you got an update from macOS v12.6 version. Please correct me if you think I might be wrong.
Just like a plus, update your Node package at least to v18.x. I hope that helps.

Related

React Native doesn't recognize the ruby version of rvm

I'm trying to correct the issue in my react native setup, the issue seems to be ruby.
To clarify I'm on a Mac M1
So i installed rvm, installed rvm 2.7.6 (which is the current version of ruby react native uses, information taken on their website). I did this command on Rosetta2 because it was crashing in a non-rosetta terminal : rvm install 2.7.6
The rest of the command are NOT done in Rosetta2.
Then I added rvm to the my ~/.zshrc file
export PATH="$PATH:$HOME/.rvm/gems/ruby-2.7.6/bin"
export PATH="$PATH:$HOME/.rvm/bin"
well actually, I added those two lines with the command rvm get stable --auto-dotfiles
Sometimes, I still get this error, I have to admit that I don't know why, I understood that the line above was supposed to add it to the path. Warning! PATH is not properly set up, /Users/myusername/.rvm/gems/ruby-2.7.6/bin is not at first place.
Anyway, I do this then :
rvm --default use 2.7.6
ruby --version
the last line return this : ruby 2.7.6p219 (2022-04-12 revision c9c2245c0a) [x86_64-darwin22]
which sounds okay to me, so I try to init a new project with react native : npx react-native init NewProject
Then I got something suspicious, react native telling me to download cocoapods either with gem or home-brew, but I already did it with gem. Anyway I select download with gem (or Homebrew, both result have the same error). And I got this error : Your Ruby version is 2.6.10, but your Gemfile specified 2.7.6
Re-checked the ruby version, still the 2.7.6, I'm missing something, and maybe more than just one thing but I've been on a lot of post and stuff and can't find the solution so I'm trying here.
have you tried to remove the /usr/local/bin/bundle file and then run again ?
source : https://github.com/facebook/react-native/issues/35873#issuecomment-1397226452
Here are some alternative you can try too :
Tutorial for ruby with rbenv : https://nnomadic.medium.com/how-to-address-problems-with-ruby-cocoapods-and-react-native-cli-on-m1-macbooks-88804f6de06
Workaround with rbenv : React Native Ruby version error even If I have the correct version installed
Installing cocoapods (after ruby is installed) : How do I install CocoaPods?

Rubocop installation (machine: linux-gnu, Ubuntu)

I go through the process of installing the rubocop gem install rubocop --version 0.86.0
And run rubocop -v afterwards to make sure everything is fine.
Instead, I receive the message below:
warning: parser/current is loading parser/ruby27, which recognizes
warning: 2.7.2-compliant syntax, but you are running 2.7.0.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
1.8.1
From what I can understand with my limited knowledge, it says that my ruby version is not compatible. Is that right? That I'm using 2.7.0 and I need to use 2.7.2 or above.
I run rvm ls
=* ruby-2.7.2 [ x86_64 ]
Then I try to run ruby -v
ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu]
I've gone through the process of rvm install 2.7.2 & rvm use 2.7.2 I have toggled-on 'Run command as a login shell' - because that was the only way I could get 'rvm' to work in the terminal.
If someone is able to help me with how I can upgrade my ruby version, it would be greatly appreciated.
Sidenote - I tried to follow the link https://github.com/whitequark/parser#compatibility-with-ruby-mri. 1.8.1 and I willingly admit I don't understand what's going on, on this page or how I can use it to solve the problem.
Lucas R
You can safely ignore this warning. The parser gem takes things very seriously; it is detecting that you are running a different patch version than it expects (2.7.2 instead of 2.7.0), but there are normally no syntax changes between patch versions.
Unrelated note: rubocop 0.86 is very old; you should upgrade if you can.

Openshift and net-ssh incompatibility? (2.9.3-beta1 vs 2.9.2)

by searching to access my Postgres DB on Openshift, i'm currently facing problem using net-ssh.
At this step - note that the installed Ruby version is 2.2.0 and net-ssh is 2.9.3-beta1
To be able to access the DB from my local DB IDE, i need to execute:
rhc port-forward myappname
But the execution returns this error: Checking available ports ... Could not parse PKey: no start line
As you can see in this post (an other ones e.g. this one), the fix is to back to a stable version of net-ssh. the 2.9.2.
What i've succesfully done.
But now, running rhc port-forward myappname is giving me the following error: .../2.2.0/rubygems/core_ext/kernel_require.rb:54:in 'require': cannot load such file
And the fix is to upgrade net-ssh to the 2.9.3-Beta1 version (see this post).
This is really weird! Seems that "the snake is biting its own tail" (don't know if that french expression got english translation).
Note that i've tried to make a clean setup with new ssh key gen (automatically and manually).
My system is runnin' Win 7 64bits.
I made uninstall/install of last version of Ruby.
Reinstall of rhc.
Last version running on rhc-1.36.4. The problem goes on.
Can you help?
Should i install an older version of ssh-net and/or Ruby (i'm not allowed to use ssh-net 2.5.2 due to new version of rhc)?
(sorry for my bad english)
rhc/Gemfile & rhc/rhc.gemspec required gem "net-ssh", "<= 2.9.2"
net-ssh version 2.9.2 use require dl/import atleast on pageant.rb
dl/import is removed from ruby see https://github.com/ruby/ruby/blob/v2_2_0/NEWS#L148-L149
instead fiddle is recommended
net-ssh 3.* seems to fix this(uses fiddle/{import,{ for ruby >= 2.1)
net-ssh version 3. seems to have drop in compatibility(still working on mine) for rhc
So a simple hack is to modify rhc/Gemfile & rhc/rhc.gemspec and install the gem
A guy already have done it.
A Solution(Untested)
gem 'rhc', :git => 'git://github.com/thrasher-redhat/rhc.git'
from https://stackoverflow.com/a/7421712/2382629
Alternative Solution(Tested even on windows 7 32bit :p)
git clone https://github.com/openshift/rhc
cd rhc
modify rhc/Gemfile & rhc/rhc.gemspec like https://github.com/openshift/rhc/pull/748/files then
gem build rhc.gemspec
it should output like
blah! blah! blah! warnings and msgs......
Successfully built RubyGem
Name: rhc
Version: 1.38.4
File: rhc-1.38.4.gem
then run
gem install rhc-1.38.4.gem
You need to use an older version of Ruby, try 1.9.3 or 2.0, or maybe even 2.1.

Jekyll on Windows Liquid Exception: Failed to get header

I'm trying to use Jekyll on my windows 7 (64bit) PC.
I have installed Ruby, Ruby Devkit, Python 2.7, Jekyll and Pygments but getting this error
E:\jekyll\my-site>jekyll serve
Configuration file: E:/jekyll/my-site/_config.yml
Source: E:/jekyll/my-site
Destination: E:/jekyll/my-site/_site
Generating... Liquid Exception: Failed to get header. in 2013-07-19-welcome-to-jekyll.markdown
error: Failed to get header.. Use --trace to view backtrace
I also got this error, and a couple of other similar errors too, and finally got to a solution: you need to have a couple of compatible versions of the required Ruby, Python and Pygments.
Install Ruby 1.9.3-p448 version (download here);
Install Python 2.7.5 version (download here);
Install Pygments 0.5.0
gem uninstall pygments.rb
gem install pygments.rb --version "=0.5.0"
I hope it helps.
Edited: Don't forget to add the correct PATHs to your system variables. In my case, it was:
C:\Python27;C:\Ruby193
In order to improve this content, there is a simple tutorial (written in Portuguese, but I guess you can understand the steps, always considering the versions of software/plugins listed above) - view tutorial.
Another possible cause for this error message on Windows is that the path to the Pygments scripts contains spaces. Took me a while to figure this one out...
For my situation, install pygments 0.5.0 or 0.5.4 both have problem. I fixed by re-install python 2.7.6. Please refer to following answer:
https://github.com/jekyll/jekyll/issues/1181#issuecomment-35963876
I had two versions of python installed on my system.(Windows 8.1)
Python22 and Python27.
I removed Python22, added Python27 to System variables and issue got fixed.

"Quick Install Gem" not working on RubyMine

I've just done a fresh install of RubyMine 4.5 in order to get a quickstart on Rails dev.
Whenever I try and install any Gem using the Tools > Quick Install Gem... command, I get the following error (below is specific to the flickraw gem)
Failed to Install Gems
Following gems were not installed:
flickraw(0.9.6): While executing gem ...
(Errno::EACCESS)
Permission denied - /Users/Andy/.rvm/gems/ruby-1.9.3-p194/cache/flickraw-0.9.6.gem
I guess I get that it's a permissions error...but why is it happening, shouldn't this just work? And how do I fix it?
I'm running this on the latest version of OSX Mountain Lion.
I've had similar problems before, it turned out to be caused by sudo being the owner of some gems installed in that rvm ruby installation I was using. I guess I installed something with sudo by accident, I dunno-- but go check in /Users/Andy/.rvm/gems/ruby-1.9.3-p194/cache and /Users/Andy/.rvm/gems/ruby-1.9.3-p194/gems and see if sudo owns cache/flickraw-0.9.6.gem or any folders in gems and if needed change the owner and group back to you ... I actually had so many messed up I opted to just remove and rebuild that ruby.

Resources