-
Notifications
You must be signed in to change notification settings - Fork 154
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
Failed to activate asdf environment #1999
Comments
👋 This seems like the same issue as #1990 which was solved by updating |
Thanks. And how was |
In the latest release, we start printing invalid JSON environments to the output tab to make this type of problem easier to diagnose. Could you please give it a try and report what the extension tried to parse as the environment? |
Based on what I could gather, it seems that I think we can try to run exec with the shell identified by VS Code, which I'm exploring on this PR #2006. @davijonm it would be extremely helpful if you could confirm that this fixes the issue. You can do so by following these steps:
|
I use zsh but asdf is set in both .zshrc and .bashrc files |
Not sure why it still used |
Hey guys, any updates? |
@davijonm we're still investigating. For now, you can downgrade to v0.5.19 of the extension to switch to the older activation approach. |
I just realized I made a mistake in the previous iteration of #2006. I set the Could you please try again and report if that fixes it? |
Ok, I tried again. After step 5, a new window opened and apparently there was no error, but I can't tell if it worked because the main window still shows this error: /home/davi/.asdf/asdf.sh: [[: not found |
Vscode, asdf and Ruby LSP are all in the latest versions
Code snippet or error message
VS code message: Failed to activate asdf environment: Unexpected token '/', "/bin/sh: 2"... is not valid JSON
The text was updated successfully, but these errors were encountered: