environment: line 1: set_node_version: command not found

[jaderzanotti]

Hi team
I am really no expert in Linux, I am the opposite of that

so here is my problem in my Intel i7 running Ubuntu in a MacOS via Colima/Vagrant:

❯ rbenv install 3.0.7 --verbose
environment: line 1: set_node_version: command not found

BUILD FAILED (Ubuntu 22.04 on x86_64 using ruby-build 20241017)

and

ruby-build on  master 
❯ ruby-build 3.0.7 /usr/local/rbenv/version/3.0.7 --verbose
environment: line 1: set_node_version: command not found

BUILD FAILED (Ubuntu 22.04 on x86_64 using ruby-build 20241017)

more info:

❯ rbenv root
/usr/local/rbenv

~ 
❯ ls $(rbenv root)/plugins
ruby-build

~ 
❯ which -a ruby-build rbenv-install
/usr/local/rbenv/plugins/ruby-build/bin/ruby-build
/usr/local/rbenv/plugins/ruby-build/bin/ruby-build
/usr/bin/ruby-build
/bin/ruby-build
/usr/local/rbenv/plugins/ruby-build/bin/rbenv-install
/usr/local/rbenv/plugins/ruby-build/bin/rbenv-install

and the versions output of rbenv and ruby-build

ruby-build --definitions
1.8.5-p52
1.8.5-p113
1.8.5-p114
<< I am cropping outputs here >>
3.0.2
3.0.3
3.0.4
3.0.5
3.0.6
3.0.7                        << this is the one I want >>
3.1.0-preview1
3.1.0
3.1-dev
3.1.1
<< I am cropping outputs here >>

❯ rbenv versions
  2.6.6
  2.6.8
  2.7.3
  3.0.1
  3.0.2
* 3.0.3 (set by /usr/local/rbenv/version)
  3.1.1
  3.2.2
  
❯ rbenv install --list-all
1.8.5-p52
1.8.5-p113
1.8.5-p114
<< I am cropping outputs here >>
3.0.2
3.0.3
3.0.4
3.0.5
3.0.6
3.0.7                     << this is the one I want >>
3.1.0-preview1
3.1.0
3.1-dev

and showing my ruby-build plugin and rbenv is updated:

❯ cd /usr/local/rbenv

rbenv on  master 
❯ git pull
Already up to date.

rbenv on  master took 2s 
❯ cd plugins/

rbenv/plugins on  master 
❯ git pull
Already up to date.

rbenv/plugins on  master 
❯ cd ruby-build

ruby-build on  master 
❯ git pull
Already up to date.

In environment: line 1: set_node_version: command not found I have no idea about this environment and set_node_version errors. I could not find anything useful here in Discussions or in Stackoverflow, unfortunately

Any hints will be appreciated
Thank you

[mislav]

In environment: line 1: set_node_version: command not found I have no idea about this environment and set_node_version errors. I could not find anything useful here in Discussions or in Stackoverflow, unfortunately

This is very strange; I haven't seen this before either. I have no idea what environment is or where set_node_version is coming from. I suspect it's some kind of rogue script on your system that somehow gets invoked during ruby-build operation, but I can't tell where or how.

Just casually using rbenv or ruby-build to list information doesn't seem to trigger it. It specifically seems to come up only during the installation process for you. What you could do is temporarily enable bash debug mode for the ruby-build script:

# edit the /usr/local/rbenv/plugins/ruby-build/bin/ruby-build script and
# put this near the top:
set -x

Now call rbenv install ... again (rbenv install is just a thin wrapper for the ruby-build command) and this will write the current bash command being processed to stderr as ruby-build is getting executed. The output will be very verbose, but you will be able to see what happens just before the environment: line 1 error. You could share with us the last few lines of output before that error. Thanks!

[mislav]

Thanks. Do you use direnv or some other tool to automatically run shell functions when you cd into a directory? I see set_node_version happening after a pushd call. Do you have BASH_ENV environment variable set by any chance?

[jaderzanotti]

thanks for your reply
hmm, no BASH_ENV content

foo-bar on  develop via 💎 v3.2.2 
❯ echo $BASH_ENV


foo-bar on  develop via 💎 v3.2.2 
❯ direnv
bash: direnv: command not found

foo-bar on  develop via 💎 v3.2.2 
❯ 

sorry to ask you that, but can you please send me some commands to check if I have direnv installed in my Ubuntu? I really don't know

[mislav]

direnv was just a guess—if you don't know what it is, you likely don't have it installed. If it was installed, your shell initialization files like .bashrc or .bash_profile/.profile would have loaded it.

Can you try searching for the string set_node_version on your system? Something like:

grep set_node_version ~/.* /etc/* /etc/profile.d/*

This will yield some typical directory read errors, but if there is a file containing that script in the listed directories, it will find it.

You could also try searching for a file literally named "environment" on your system:

find / -type f -name environment

[jaderzanotti]

hey, Happy Friday
so I ran grep set_node_version ~/.* /etc/* /etc/profile.d/*
removing all the grep: xxxxxxx: Is a directory results:

/home/vagrant/.bashrc:function set_node_version {
/home/vagrant/.bashrc:  set_node_version
/home/vagrant/.bashrc:  set_node_version
/home/vagrant/.bashrc:  set_node_version

then I cat ~/.bashrc and the relevant part is:

function set_node_version {
        if test -f "./package.json"; then
                if test -f "./.nvmrc"; then
                        nvm use
                        return;
                fi

                nvm use default
        fi
}

function cd {
        builtin cd "$@" || return

  set_node_version
}

function pushd {
        builtin pushd "$@" || return

  set_node_version
}

function popd {
        builtin popd "$@" || return

  set_node_version
}

for find / -type f -name environment, excluding the 'Permission denied' results, I have:

❯ find / -type f -name environment
/home/linuxbrew/.linuxbrew/Cellar/linux-pam/1.7.0/.bottle/etc/environment
/home/linuxbrew/.linuxbrew/etc/environment
/etc/environment
/usr/share/rvm/scripts/functions/environment
/usr/share/rvm/rubies/ruby-3.0.3/lib/ruby/gems/3.0.0/environment
/usr/share/rvm/rubies/ruby-2.6.6/lib/ruby/gems/2.6.0/environment
/usr/share/rvm/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/environment
/usr/share/rvm/rubies/ruby-3.0.7/lib/ruby/gems/3.0.0/environment
/usr/share/rvm/rubies/ruby-3.1.6/lib/ruby/gems/3.1.0/environment
/usr/share/rvm/rubies/ruby-3.2.2/lib/ruby/gems/3.2.0/environment
/usr/share/rvm/gems/ruby-3.0.3/environment
/usr/share/rvm/gems/ruby-2.6.6/environment
/usr/share/rvm/gems/ruby-3.1.1/environment
/usr/share/rvm/gems/ruby-3.0.7/environment
/usr/share/rvm/gems/ruby-3.1.6/environment
/usr/share/rvm/gems/ruby-3.2.2/environment
/usr/share/rvm/src/rvm/scripts/functions/environment

But those rvm and linuxbrew are newer than my main error, I think. I installed these 2 tools this week

so, excited about the set_node_version findings above, I...

• removed all that 4 functions from my ~/.bashrc
• used curl -fsSL https://github.com/rbenv/rbenv-installer/raw/HEAD/bin/rbenv-installer | bash from https://github.com/rbenv/rbenv-installer#rbenv-installer
• tried rbenv install 3.1.6 again, and voilà, it's working:

==> Downloading ruby-3.1.6.tar.gz...
-> curl -q -fL -o ruby-3.1.6.tar.gz https://cache.ruby-lang.org/pub/ruby/3.1/ruby-3.1.6.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 19.9M  100 19.9M    0     0  7659k      0  0:00:02  0:00:02 --:--:-- 7659k
==> Installing ruby-3.1.6...
ruby-build: using readline from homebrew
ruby-build: using libyaml from homebrew
ruby-build: using gmp from homebrew
-> ./configure --prefix=/usr/local/rbenv/versions/3.1.6 --enable-shared --with-readline-dir=/home/linuxbrew/.linuxbrew/opt/readline --with-libyaml-dir=/home/linuxbrew/.linuxbrew/opt/libyaml --with-gmp-dir=/home/linuxbrew/.linuxbrew/opt/gmp --with-ext=openssl,psych,+ --with-jemalloc
-> make -j 12
-> make install
==> Installed ruby-3.1.6 to /usr/local/rbenv/versions/3.1.6

I can't express enough my gratitude for your guys helping me resolve this.
That error had been haunting me for months.

Thank. You. 🍺

[mislav]

Glad you got to the bottom of it.

One thing still remains puzzling, though: even though the interactive bash shell (one you type commands into) does source your ~/.bashrc, running a bash script (such as ruby-build) does not source it, and therefore the pushd override you had there should not have taken effect.

So my best guess as to what happened is that you had export -f pushd somewhere. What that would do is pass on the pushd override down to any bash subshells, including during ruby-build execution. There, pushd would have still be defined as function pushd { builtin pushd "$@" ... set_node_version }, but the set_node_version function wouldn't exist, since it was only defined in the ~/.bashrc and therefore only present in an interactive shell. Thus, an error is raised.

There should never be a reason to export -f NAME from an interactive shell unless you really know what you're doing, so I would suggest avoiding ever doing that.

[jasonkarns]

I also have no idea where set_node_version would be coming from. That is not a function that exists in nodenv's codebase (on the off chance that a nodenv plugin was somehow getting looped into rbenv hooks).

[jaderzanotti]

thank you