-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: lib/utils.bash: line 234: ASDF_.._VERSION: invalid variable name #1029
Comments
I noticed @lifeiscontent is having a similar issue in #693 (comment) |
Is this a |
I'm fairly certain this is the same as #693. Some plugin(s) names aren't properly handled and it results in this invalid variable name. |
It's new that I see it, and I've used
Hmm, what's with that |
I'm having the same issue, linked here asdf-vm/asdf-ruby#236 In my case it happens with Ruby instead, but other than that the symptoms are similar. |
The problem (at least on my side) is that running Print from my See those The workaround for me is deleting the shim script and then reshimming: rm "$ASDF_DIR/shims/npm"
asdf reshim node You might as well delete all others shims and reshim them all over again: rm "$ASDF_DIR"/shims/*
asdf reshim I don't know if this issue exists because I kept messing with symlinks in the plugins dir, or because some bug in the past created them. I think the solution should be cleaning these ghost plugins after reshims, or making a specific command for pruning/cleaning the shims directory |
@augustobmoura thanks for the comment. It appears we've got a bug somewhere in our reshim logic as I just encountered issue myself (and I'm not using any symlinks). It does appear |
I tried to debug it, but the problem is that it is not consistent. I tried manually reshimming it sometimes but never got it to write |
Does someone want to debug with me on my machine? It still does it. |
This popped up for me and I have no idea what is causing it.
|
For me rm $ASDF_DATA_DIR/plugins/.DS_Store seemed to do the trick |
@Stratus3D any ideas on why a .DS_Store file would interfere with something like this? |
Thanks for the comments @sheldonhull and @bbenzikry ! I now understand what the problem is - in your case, somewhere in the code we are looping over all files in |
@Stratus3D I had tried to fix that in December, but my approach was to clean up after :S It worked for me, but I understand that didn't really fix the problem Maybe some parts of my approach can be of use though, as I did use the plugins folder as reference of what would be valid metadata. |
@sheldonhull can you share the output of |
I'm encountering this too, but weirdly, only in CI, while invoking asdf inside a Docker image that I have previously built. Tt does not reproduce locally for me. I pasted some things you've asked others for, but I don't think the issue involves stray files under My findings: cannot identify shim as executableI narrowed it down to
However, it looks executable to me! I don't understand why the Obviously I can invoke this shim (it's how we get into the error condition in the first place!) but something makes bash 5 think it's not executable.
Marginally useful troubleshooting info
|
Update: It does seem like ASDF has some circular error case, where a stub that is non executable causes bizarre error messages (because asdf is parsing its own error output to determine something about the shim). Not a big issue though, as long as one's shims are all proper. |
@xeger thanks for the info. @sheldonhull ping. I've got a fix that I think will address the |
I've merged a possible fix for this so if you want to test it run |
Closing as I've not gotten any responses on whether this issue still exists with the latest version. I will reopen if not resolved. |
As a note, I'm getting this right now with
The error goes away if I |
@glasser please share the output of |
Note that this is after I have deleted the DS_Store file and stopped the error. |
@glasser what happens if you run |
I'll let you know if it crops up again — I don't know how to induce OSX into creating a .DS_Store file. |
Ah actually, just opening
|
Describe the Bug
When I run neovim latest
asdf
reports an invalid variable name.Steps to Reproduce
Expected Behaviour
Neovim would start with no error notice in the terminal.
Actual Behaviour
I see this error message:
Environment
OS: Linux jimmie 5.11.0-31-generic #33-Ubuntu SMP Wed Aug 11 13:19:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux SHELL: fish, version 3.1.2 ASDF VERSION: v0.8.1-a1ef92a ASDF ENVIRONMENT VARIABLES: ASDF_DIR=/home/jesse/.asdf ASDF INSTALLED PLUGINS: deno https://github.com/asdf-community/asdf-deno.git dotnet-core https://github.com/emersonsoares/asdf-dotnet-core.git elixir https://github.com/asdf-vm/asdf-elixir.git elm https://github.com/asdf-community/asdf-elm.git erlang https://github.com/asdf-vm/asdf-erlang.git haskell https://github.com/vic/asdf-haskell.git lua https://github.com/Stratus3D/asdf-lua.git neovim https://github.com/richin13/asdf-neovim.git nodejs https://github.com/asdf-vm/asdf-nodejs.git postgres https://github.com/smashedtoatoms/asdf-postgres.git python https://github.com/danhper/asdf-python.git redis https://github.com/smashedtoatoms/asdf-redis.git ruby https://github.com/asdf-vm/asdf-ruby.git rust https://github.com/code-lever/asdf-rust.git shfmt https://github.com/luizm/asdf-shfmt.git yq https://github.com/sudermanjr/asdf-yq.git
The text was updated successfully, but these errors were encountered: