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

fix: correct handling of .default-gems file #424

Merged
merged 1 commit into from
Dec 23, 2024

Conversation

Stratus3D
Copy link
Member

This PR re-works the solution in #417 so the code does not crash.

@jmschp FYI, I think this is the correct solution.

@Stratus3D Stratus3D force-pushed the tb/correct-default-gem-processing branch from d132f95 to c8f5ad2 Compare December 23, 2024 15:29
@Stratus3D
Copy link
Member Author

I tested this locally and it works with a .default-gems file that lacks a newline.

@Stratus3D Stratus3D merged commit fb86bfd into master Dec 23, 2024
4 checks passed
@jmschp
Copy link
Contributor

jmschp commented Dec 23, 2024

@Stratus3D

In what situation did it crashed?

@Stratus3D Stratus3D deleted the tb/correct-default-gem-processing branch December 23, 2024 16:57
@Stratus3D
Copy link
Member Author

For me, always, because it complained $line wasn't set. I'm not sure why, but the script is set to fail if a variable is unset - https://github.com/asdf-vm/asdf-ruby/blob/master/bin/install#L3.

@jmschp
Copy link
Contributor

jmschp commented Dec 23, 2024

Curious, it didn't fail, when I tested it.
Well its fixed anyway,

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants