"No version is set" when version is set and returned by `asdf current` [ruby] #557

barberj · 2019-08-05T20:11:57Z

Following advice from #488, creating new issue.

Steps to reproduce

Install new ruby. Attempt to install dependencies using bundler. Tried new session after install.

Expected behavior

Dependencies are installed.

Actual behavior

➜  git:(master) bundle install
asdf: No version set for command bundle
you might want to add one of the following in your .tool-versions file:

ruby 2.6.3
ruby 2.6.1

➜ git:(master) asdf current
elixir         No version set for elixir; please run `asdf <global | local> elixir <version>`
erlang         No version set for erlang; please run `asdf <global | local> erlang <version>`
ruby           2.5.1    (set by /Users/justinbarber/src/melody/.tool-versions)

➜  git:(master) cat .tool-versions
ruby 2.5.1

Environment

OS:

macOS Sierra 10.12.6

asdf version:

➜  git:(master) asdf --version
v0.7.3

The text was updated successfully, but these errors were encountered:

afeld · 2019-08-06T03:08:37Z

Try running hash -r, then trying again. asdf-vm/asdf-ruby#48 (comment)

Maintainers: I think it's worth considering clearing the bash cache (hash -r or hash -d [executable] for each executable) somewhere... not sure of the best place for that. I wasn't even aware that bash did caching, and I bet a lot of other people aren't either. Thoughts?

barberj · 2019-08-06T13:45:23Z

I'm using zsh. hash -r didn't help seem to have any effect.

yordis · 2019-08-10T17:02:32Z

Same started happening with NodeJS.

➜ node -v
asdf: No version set for command node
you might want to add one of the following in your .tool-versions file:

nodejs 10.16.1

Worth saying that I had to put .tool-versions in that particular folder closer to where I am trying to use Node by using asdf local nodejs 10.16.1 but I am not sure why.

JamesLavin · 2019-08-16T21:37:59Z

I'm having the same issue, and I noticed that it seems to happen because asdf doesn't seem to know about a version of Ruby (2.6.3) I installed via asdf today. It recommends I use one of my three previous versions of Ruby:

james@James-Precision-5520:~/Git/elixirschool$ asdf current
elixir         1.9.0-otp-22 (set by /home/james/.tool-versions)
erlang         22.0.7   (set by /home/james/.tool-versions)
ruby           2.6.3    (set by /home/james/.tool-versions)
james@James-Precision-5520:~/Git/elixirschool$ jekyll
asdf: No version set for command jekyll
you might want to add one of the following in your .tool-versions file:

ruby 2.3.7
ruby 2.4.3
ruby 2.5.1
james@James-Precision-5520:~/Git/elixirschool$ ls ~/.asdf/installs/ruby
2.3.7  2.4.3  2.5.1  2.6.3
james@James-Precision-5520:~/Git/elixirschool$ asdf list ruby
  2.3.7
  2.4.3
  2.5.1
  2.6.3

When I changed my .tool-versions to point at one of the other three (older) Ruby installs, it started working.

Hoping this information may help with debugging.

bowmanmike · 2019-09-17T14:07:15Z

Having a similar issue. I have a Node, Elixir, and Ruby versions all set in my ~/.tool-versions file. When I cd into an Elixir project, asdf current picks up the Elixir and Ruby versions from the global file, but not Node. I can resolve the issue by adding a $PROJECT/.tool-versions file with the correct Node version, but I don't want to pollute a shared repo with a file that only I'm using.

ttilberg · 2019-09-26T13:31:47Z

Here's some info about my setup where I have the same issue. I just upgraded asdf as I saw in another issue that it might have been due to an old version, but I still have the issue.

MacOS 10.14.6 Mojave
asdf installed with Brew

ttilberg:~$ which asdf
/usr/local/opt/asdf/bin/asdf

ttilberg:~$ asdf --version
v0.7.4

ttilberg:~$ cat .tool-versions
ruby 2.6.3
nodejs 10.16.0
python 3.7.4

ttilberg:~$ which python
/Users/ttilberg/.asdf/shims/python

ttilberg:~$ which pip
/Users/ttilberg/.asdf/shims/pip

ttilberg:~$ python --version
Python 3.7.4

ttilberg:~$ pip install ipython
Requirement already satisfied: ipython in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (7.8.0)
Requirement already satisfied: pygments in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (2.4.2)
Requirement already satisfied: appnope; sys_platform == "darwin" in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (0.1.0)
Requirement already satisfied: traitlets>=4.2 in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (4.3.2)
Requirement already satisfied: pickleshare in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (0.7.5)
Requirement already satisfied: jedi>=0.10 in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (0.15.1)
Requirement already satisfied: prompt-toolkit<2.1.0,>=2.0.0 in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (2.0.9)
Requirement already satisfied: setuptools>=18.5 in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (40.8.0)
Requirement already satisfied: decorator in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (4.4.0)
Requirement already satisfied: pexpect; sys_platform != "win32" in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (4.7.0)
Requirement already satisfied: backcall in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from ipython) (0.1.0)
Requirement already satisfied: ipython-genutils in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from traitlets>=4.2->ipython) (0.2.0)
Requirement already satisfied: six in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from traitlets>=4.2->ipython) (1.12.0)
Requirement already satisfied: parso>=0.5.0 in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from jedi>=0.10->ipython) (0.5.1)
Requirement already satisfied: wcwidth in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from prompt-toolkit<2.1.0,>=2.0.0->ipython) (0.1.7)
Requirement already satisfied: ptyprocess>=0.5 in ./.asdf/installs/python/3.7.4/lib/python3.7/site-packages (from pexpect; sys_platform != "win32"->ipython) (0.6.0)

ttilberg:~$ ipython
asdf: No version set for command ipython
you might want to add one of the following in your .tool-versions file:

python 3.6.8


ttilberg:~$ which ipython
/Users/ttilberg/.asdf/shims/ipython

ttilberg:~$ cat $(which ipython)
#!/usr/bin/env bash
# asdf-plugin: python 3.6.8
exec /usr/local/opt/asdf/bin/asdf exec "ipython" "$@"

The shim explicitly mentions py 3.6.8 in a comment -- I'm not sure if that's a magic comment, I'm guessing so. Being that my python seems to be correctly pointed to asdf+3.7 for all the above commands, I feel like something in this last file is amiss.

EDIT: The issue above was resolved by running asdf reshim.

betogrun · 2019-09-27T18:04:08Z

I'm facing the same issue after installing another ruby version with asdf.

$ asdf install ruby 2.4.3
$ asdf local ruby 2.4.3

$ ruby -v
ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-linux]

$ cat .tool-versions 
ruby 2.4.3

$ bundle install
asdf: No version set for command bundle
you might want to add one of the following in your .tool-versions file:

ruby 2.6.1
ruby 2.6.3

Running asdf reshim ruby and restarted the terminal didn't fix the issue.
asdf version is 0.7.4

fahmifan · 2019-10-03T03:07:28Z

I also get this issue for nodejs in mac, i solve it by adding .tool-versions

cat ~/.tool-versions
nodejs 10.15.3

betogrun · 2019-10-03T15:02:04Z

I'm facing the same issue after installing another ruby version with asdf.
$ asdf install ruby 2.4.3
$ asdf local ruby 2.4.3

$ ruby -v
ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-linux]

$ cat .tool-versions 
ruby 2.4.3

$ bundle install
asdf: No version set for command bundle
you might want to add one of the following in your .tool-versions file:

ruby 2.6.1
ruby 2.6.3
Running asdf reshim ruby and restarted the terminal didn't fix the issue.
asdf version is 0.7.4

As mentioned here, the problem happens because there is no bundler for the new ruby version. Running gem install bundler solves the issue.

christopher-dG · 2019-10-04T06:06:23Z

Having this issue with Julia 1.3.0-rcX (for X = 1:3). as well as 1.1.0-rc2. I've never had any issues with normal x.y.z versions.

heydonovan · 2019-11-05T18:52:11Z

I'm experiencing the same with the terraform plugin. This just started happening this week:

$ terraform version
asdf: No version set for command terraform
you might want to add one of the following in your .tool-versions file:

terraform 0.12.2
terraform 0.12.3
terraform 0.12.5
terraform 0.12.6
terraform 0.12.7
terraform 0.12.8

$ cat ~/.tool-versions
helm 2.9.1
terraform 0.12.13

Adding it to the file instructed has no effect.

webkay · 2019-11-16T05:00:00Z

In my case, there was an error when I tried gem install bundler

$ gem install bundler
asdf: No version set for command gem

But it was solved by asdf list-all and reinstall

asdf list-all ruby
asdf uninstall ruby 2.6.2
asdf install ruby 2.6.2

tispratik · 2019-12-15T00:00:18Z

I had the same issue after asdf upgrade from 0.7.0 to 0.7.5. Turns out that my shell's rc file was still pointing at the old version.

Before fix
source /usr/local/Cellar/asdf/0.7.0/asdf.fish

After fix
source /usr/local/Cellar/asdf/0.7.5/asdf.fish

yordis · 2019-12-31T13:16:39Z

When you google the problem and realized your answer is how you fix it: #557 (comment) 😆 😆 😆 😆 classic

Any updates on this?

Also, I am doing the following in my zsh

if [[ -f "$HOME/.asdf/asdf.sh" ]] then
  source "$HOME/.asdf/asdf.sh"
  source "$HOME/.asdf/completions/asdf.bash"
fi

Therefore, I don't think I am running into the issue that @tispratik ran into.

yordis · 2019-12-31T15:14:06Z

Something I found, doing asdf current

➜ asdf current
elixir         1.9.1    (set by /Users/ubi/.tool-versions)
erlang         22.0     (set by /Users/ubi/.tool-versions)
golang         1.13.5   (set by /Users/ubi/.tool-versions)
nodejs         version 6.10 is not installed for nodejs 
rust           1.28.0   (set by /Users/ubi/.tool-versions)

This is wrong

nodejs         version 6.10 is not installed for nodejs

In fact I do have NodeJS specify in my .tool-versions

➜ cat ~/.tool-versions              
erlang 22.0
elixir 1.9.1
nodejs 10.17.0
ruby 2.6.3
clojure 1.10.0
golang 1.13.5
rust 1.28.0

I am not sure where 6.10 is coming from, continue the debugging.

yordis · 2019-12-31T15:32:37Z

Alright,

I changed ~/.asdfrc

➜ cat ~/.asdfrc 
legacy_version_file = no

I had yes before.

It seems that now asdf is able to pick ~/.tool-versions correctly now.

And I figured out somebody was using .nvmrc 🤷‍♂ 🤦‍♂

brock-noah · 2020-03-27T22:24:33Z

In relation to NodeJS, my issue was the globally installed yarn was for node v10 and not v12.

I was experiencing something like this even with the version specified.

➜ yarn
asdf: No version set for command yarn
you might want to add one of the following in your .tool-versions file:

nodejs 12.16.1

This path existed for my previous version of node 10 but not for node 12.

test -e ~/.asdf/installs/nodejs/12.16.1/.npm/lib/node_modules/yarn/ && echo OK || echo NOT FOUND

After asdf local nodejs 12.16.1 a npm install -g yarn resolved my issue.

pdgonzalez872 · 2020-06-12T10:06:13Z

Hi! I'm on OSX (Mojave 10.14.6) and ran into the following:

~ :> asdf version
v0.7.8-4a3e3d6
~ :> asdf current
elixir         1.9.4    (set by /Users/pdg/.tool-versions)
erlang         22.3.4.1 (set by /Users/pdg/.tool-versions)
~ :> asdf reshim
~ :> cat .tool-versions
erlang 22.3.4.1
elixir 1.9.4
~ :> iex
asdf: No preset version installed for command erl
Please install the missing version by running one of the following:

asdf install erlang 22.3.4.1

or add one of the following in your .tool-versions file:

erlang 22.0.7
erlang 22.2.8
~ :> asdf install erlang 22.3.4.1
erlang 22.3.4.1 is already installed
~ :> rm .tool-versions
~ :> echo "erlang 22.2.8
> elixir 1.9.4" > .tool-versions
~ :> cat .tool-versions
erlang 22.2.8
elixir 1.9.4
~ :> iex
Erlang/OTP 22 [erts-10.6.4] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe]

Interactive Elixir (1.9.4) - press Ctrl+C to exit (type h() ENTER for help)
iex(1)>
BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
       (v)ersion (k)ill (D)b-tables (d)istribution
^C~ :>

Does anyone know how I can set the correct version on .tool-versions?

pdgonzalez872 · 2020-06-12T11:42:59Z

My issue above was solved here: #662 (comment). Uninstall, use the correct plugin env vars and then installing it again solved my problem. I believe I had a bad install and had things in a weird state.

Thanks for helping @Stratus3D !

kaka-ruto · 2020-06-15T21:28:47Z

gem update --system solved for me

jthegedus · 2020-09-08T04:49:09Z

Is this considered resolved? If not, can someone please rehash the problem clearly for me as I cannot see anything in particular outstanding?

betogrun · 2020-09-08T11:46:30Z

It seems this happened because we forgot to add the packager manager (bundler for ruby, yarn for node) after adding a new version.
I also wrote a post about this: http://blog.albertorocha.me/posts/asdf-ruby-no-version-set
Hope it helps.

meymeynard · 2020-10-17T02:55:20Z

Also happened to me, solved it by just using

asdf reshim ruby

wliang002 · 2020-11-03T06:33:48Z

Set Current Version: resource: https://asdf-vm.com/#/core-manage-versions
asdf global <name> <version> [<version>...] asdf shell <name> <version> [<version>...] asdf local <name> <version> [<version>...]
global writes the version to $HOME/.tool-versions.
shell set the version to an environment variable named ASDF_${LANG}_VERSION, for the current shell session only.
local writes the version to $PWD/.tool-versions, creating it if needed.

asdf global elixir 1.2.4

amandaclarck · 2020-11-30T13:07:15Z

For me what it worked:

Reinstall ruby 2.4.4 (the version that I needed)
Restart the terminal
asdf reshim ruby / asdf reshim
gem install bundler
bundle install

A mix of everything...

pravin · 2021-04-19T21:48:39Z

try asdf reshim

Unfortunately didn't work (tried reshim in the pasted code above). Any other suggestions?

jthegedus · 2021-04-26T07:44:05Z

@pravin have you run asdf install python 2.7.18? 3.9.4 is found on your system, but not the version set in your .tool-versions file.

If that does not work and no suggestions in this thread solve the issue for you, can you open a new issue?

RobLoach · 2021-09-22T16:20:24Z

asdf global <plugin> latest fixed it for me.

willyjie23 · 2021-11-06T06:12:13Z

gem install rails --your_version fixed it for me.

surhidamatya · 2021-12-27T05:54:59Z

I faced the same issue for node what I did was

Create .tool-versions in home directory
asdf global nodejs 16.13.0

and it fixed the issue
Note: I am using M1 Mac mini

ealasgarov · 2022-04-21T09:07:00Z

you need to set a version in a format "asdf global package-name 0.0.0"

oviliz · 2022-06-21T14:28:25Z

This is just rubbish...

dbrtly-upguard · 2022-07-20T23:51:39Z

I faced the same issue for node what I did was

Create .tool-versions in home directory

asdf global nodejs 16.13.0

and it fixed the issue Note: I am using M1 Mac mini

In my case it was direnv 2.32.1.
Would help if there was a suggestion to append the global version file on install of a plugin.

Joseph-Burke · 2022-08-10T04:32:38Z

I'm facing the same issue after installing another ruby version with asdf.
$ asdf install ruby 2.4.3
$ asdf local ruby 2.4.3

$ ruby -v
ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-linux]

$ cat .tool-versions 
ruby 2.4.3

$ bundle install
asdf: No version set for command bundle
you might want to add one of the following in your .tool-versions file:

ruby 2.6.1
ruby 2.6.3
Running asdf reshim ruby and restarted the terminal didn't fix the issue.
asdf version is 0.7.4
As mentioned here, the problem happens because there is no bundler for the new ruby version. Running gem install bundler solves the issue.

This helped me get my solution. I was trying to run rails new, which only started working after gem install rails and gem install rails

trufan-poe · 2022-09-23T18:45:52Z

Has this problem with nodejs and yarn. I ran yarn install and got that error. Reinstalling yarn with asdf resolved the problem. The previous yarn I used was installed via npm.

liyicky · 2022-11-29T11:27:24Z

I had to uninstall the older version I was using in order to get things working again.

No preset version installed for command foreman
Please install a version by running one of the following:

asdf install ruby 3.1.2

or add one of the following versions in your config file at /Users/liyicky/.tool-versions
ruby 3.1.0

asdf uninstall ruby 3.1.0

fredrivett · 2022-12-06T10:32:06Z

For those that miss the obvious (like me), if you're trying to install dependencies with yarn then remember to actually install yarn for that version of node before trying to use it, with npm install -g yarn:

$ asdf install nodejs 16.3.0

$ yarn
> No preset version installed for command yarn
> Please install a version by running one of the following:
> asdf install nodejs 16.3.0
> or add one of the following versions in your config file at /[redacted]/.tool-versions
nodejs 16.18.1

$ node -v
> 16.3.0

$ npm install -g yarn

$ yarn
> // successfully installs

jthegedus · 2022-12-12T03:56:10Z

Just to add to what @fredrivett suggested, asdf has a plugin for Yarn, so your version of Yarn and Node.js can be managed independently instead of having to re-install yarn globally each time you change node version.

kenny-evitt · 2023-03-24T19:43:03Z

I ran into this issue (or rather a relative of it) just now with Node.js (and Gulp) and what seems to have worked was to run asdf reshim nodejs VERSION where VERSION is the (new) version I wanted to use:

✔ ~/my_code [my-branch|✚ 1] 
(ins)15:34 $ asdf shim-versions gulp
nodejs 6.11.4
nodejs 12.18.3
✔ ~/my_code [my-branch|✚ 1] 
(ins)15:34 $ asdf reshim nodejs 19.8.1
✔ ~/my_code [my-branch|✚ 1] 
(ins)15:35 $ asdf shim-versions gulp
nodejs 6.11.4
nodejs 12.18.3
nodejs 19.8.1

DRAKYULA · 2023-04-06T19:12:53Z

I ran into this issue and tried all of the above solutions, as well as some that my co-workers suggested, like removing ~/.asdf/shims. None of the above worked. Eventually, what seemed to work for me was removing the asdf ruby plugin (asdf plugin remove ruby), adding it back (asdf plugin add ruby https://github.com/asdf-vm/asdf-ruby.git ), and re-installing ruby (also gem install bundler and bundle install) and finally re-running the command I was trying to in the first place. Hopefully this helps someone in the future!

assadk88 · 2023-04-18T11:15:56Z

I ran into this issue and tried all of the above solutions, as well as some that my co-workers suggested, like removing ~/.asdf/shims. None of the above worked. Eventually, what seemed to work for me was removing the asdf ruby plugin (asdf plugin remove ruby), adding it back (asdf plugin add ruby https://github.com/asdf-vm/asdf-ruby.git ), and re-installing ruby (also gem install bundler and bundle install) and finally re-running the command I was trying to in the first place. Hopefully this helps someone in the future!

This was the only thing that worked for me too – thanks!

m-graf · 2023-04-25T18:54:45Z

For those that miss the obvious (like me), if you're trying to install dependencies with yarn then remember to actually install yarn for that version of node before trying to use it, with npm install -g yarn:
$ asdf install nodejs 16.3.0

$ yarn
> No preset version installed for command yarn
> Please install a version by running one of the following:
> asdf install nodejs 16.3.0
> or add one of the following versions in your config file at /[redacted]/.tool-versions
nodejs 16.18.1

$ node -v
> 16.3.0

$ npm install -g yarn

$ yarn
> // successfully installs

This is the only thing that worked. Comical.

LucasDachman · 2023-06-16T15:34:50Z

Uninstalling and reinstalling worked for me

asdf uninstall ruby 2.5.3
asdf install ruby 2.5.3

haider792 · 2023-10-29T14:09:47Z

if you working on CI/CD pipeline and facing ruby version issue,
press "CMD + SHIFT + ." in your project folder on mac,
you will see the hidden files after that you will be shown .ruby-version file, open it and update the version needed on the CI/CD.
push the code in repo.
everything will be good then

emmanuelkamala · 2024-01-10T22:30:44Z

In my case, there was an error when I tried gem install bundler
$ gem install bundler
asdf: No version set for command gem
But it was solved by asdf list-all and reinstall
asdf list-all ruby
asdf uninstall ruby 2.6.2
asdf install ruby 2.6.2

Thank you, this solved my problem!

jsatk · 2024-01-16T22:38:14Z

I am once again encountering this issue w/ ruby. I've tried everything here (reinstalls, reshims, restarts) still no dice.

jmjohnson · 2024-01-19T19:37:22Z

For what it's worth, I encountered this error today; hash -r and asdf reshim ruby worked for me.

But I swear I tried it once and it didn't work.

corrieleech · 2024-03-21T20:04:50Z

Adding here for anyone else silly enough to forget, but running bundle install to align your Gemfile.lock with the new version of ruby also helps. 🤦‍♀️

soubhik-c · 2024-04-17T19:54:06Z

#557 (comment)
worked for me.

mateuseap · 2024-05-17T14:37:53Z

I've tried a lot of solutions, but only the one given in #557 (comment) worked for me. Thanks a lot, @DRAKYULA!

johndunlap · 2024-05-23T02:09:06Z

asdf global <plugin> latest fixed it for me.

This worked for me. Thank you!

Stratus3D added the bug label Oct 3, 2019

ttilberg mentioned this issue Oct 3, 2019

"No version set for command bundle" when trying to add Ruby 2.5.5 to my toolchest asdf-vm/asdf-ruby#127

Closed

Stratus3D mentioned this issue Mar 2, 2020

"No version set for command" has unhelpful error message #662

Closed

jonaustin added a commit to jonaustin/dotfiles that referenced this issue Mar 17, 2020

https://github.com/asdf-vm/asdf/issues/557

ce6bec7

polarathene mentioned this issue Aug 3, 2020

"asdf: No preset version installed for command which" #769

Closed

jthegedus changed the title ~~"No version is set" when version is set and returned by asdf current.~~ "No version is set" when version is set and returned by asdf current [ruby] Apr 26, 2021

jthegedus mentioned this issue Apr 26, 2021

"No preset version installed, Please install a version" when version is already installed [golang] #914

Closed

Stratus3D mentioned this issue Oct 26, 2021

bug: Although system Python version matches .tool-versions in a git repo, it is not picked up. #1069

Open

booty mentioned this issue Mar 9, 2022

bug: "No preset version installed" when version is already installed [ruby] #1181

Closed

"No version is set" when version is set and returned by asdf current [ruby] #557

"No version is set" when version is set and returned by asdf current [ruby] #557

Comments

barberj commented Aug 5, 2019

Steps to reproduce

Expected behavior

Actual behavior

Environment

afeld commented Aug 6, 2019

barberj commented Aug 6, 2019 • edited Loading

yordis commented Aug 10, 2019 • edited Loading

JamesLavin commented Aug 16, 2019

bowmanmike commented Sep 17, 2019

ttilberg commented Sep 26, 2019 • edited Loading

betogrun commented Sep 27, 2019

fahmifan commented Oct 3, 2019

betogrun commented Oct 3, 2019

christopher-dG commented Oct 4, 2019

heydonovan commented Nov 5, 2019 • edited Loading

webkay commented Nov 16, 2019

tispratik commented Dec 15, 2019

yordis commented Dec 31, 2019

yordis commented Dec 31, 2019 • edited Loading

yordis commented Dec 31, 2019 • edited Loading

brock-noah commented Mar 27, 2020

pdgonzalez872 commented Jun 12, 2020

pdgonzalez872 commented Jun 12, 2020

kaka-ruto commented Jun 15, 2020

jthegedus commented Sep 8, 2020

betogrun commented Sep 8, 2020

meymeynard commented Oct 17, 2020 • edited Loading

wliang002 commented Nov 3, 2020

asdf global elixir 1.2.4

amandaclarck commented Nov 30, 2020 • edited Loading

pravin commented Apr 19, 2021

jthegedus commented Apr 26, 2021

RobLoach commented Sep 22, 2021

willyjie23 commented Nov 6, 2021

surhidamatya commented Dec 27, 2021

ealasgarov commented Apr 21, 2022

oviliz commented Jun 21, 2022

dbrtly-upguard commented Jul 20, 2022

Joseph-Burke commented Aug 10, 2022 • edited Loading

trufan-poe commented Sep 23, 2022

liyicky commented Nov 29, 2022

fredrivett commented Dec 6, 2022

jthegedus commented Dec 12, 2022

kenny-evitt commented Mar 24, 2023

DRAKYULA commented Apr 6, 2023

assadk88 commented Apr 18, 2023

m-graf commented Apr 25, 2023

LucasDachman commented Jun 16, 2023

haider792 commented Oct 29, 2023 • edited Loading

emmanuelkamala commented Jan 10, 2024

jsatk commented Jan 16, 2024

jmjohnson commented Jan 19, 2024

corrieleech commented Mar 21, 2024

soubhik-c commented Apr 17, 2024

mateuseap commented May 17, 2024

johndunlap commented May 23, 2024

"No version is set" when version is set and returned by `asdf current` [ruby] #557

"No version is set" when version is set and returned by `asdf current` [ruby] #557

barberj commented Aug 6, 2019 •

edited

Loading

yordis commented Aug 10, 2019 •

edited

Loading

ttilberg commented Sep 26, 2019 •

edited

Loading

heydonovan commented Nov 5, 2019 •

edited

Loading

yordis commented Dec 31, 2019 •

edited

Loading

yordis commented Dec 31, 2019 •

edited

Loading

meymeynard commented Oct 17, 2020 •

edited

Loading

amandaclarck commented Nov 30, 2020 •

edited

Loading

Joseph-Burke commented Aug 10, 2022 •

edited

Loading

haider792 commented Oct 29, 2023 •

edited

Loading