[go: nahoru, domu]

Skip to content
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

--yjit added to ruby command when not supported (with asdf usage) #2027

Closed
addbrick opened this issue May 9, 2024 · 2 comments
Closed

--yjit added to ruby command when not supported (with asdf usage) #2027

addbrick opened this issue May 9, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@addbrick
Copy link
addbrick commented May 9, 2024

Description

Reproduction steps

I am using the vscode extension for a project running ruby 2.7.7, so I am following the separate Gemfile usage. The project uses asdf to manage ruby versions. This has been working great but it broke with the vscode extension version 0.5.20.

Now when I start the extension in this project, it shows an error /Users/addisonbrickey/.asdf/installs/ruby/2.7.7/bin/ruby: invalid option --yjit (-h will show valid options) (RuntimeError).

The core of the issue is the --yjit option is being added to the ruby command even though ruby 2.7.7 does not support it. I did notice in that release a manager for asdf was introduced #1845 in 0.5.20. My project uses asdf so I assume that is part of the issue. Can see the code building the ruby command checks the ruby version number to ensure it supports yjit option.

@addbrick addbrick added the bug Something isn't working label May 9, 2024
@vinistock
Copy link
Member

Thank you for the bug report. We released v0.7.0 with a few ASDF related fixes. Can you please try it and let us know if you find any issues?

@vinistock
Copy link
Member

This should be fixed in the latest versions of the extension. Please let us know if that's not the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants