Add callout on editors section of website about Mason risks #2885
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When using Mason to manage Ruby LSP, unless only a single Ruby version is used, there are chances of strange errors due to conflicts of the Ruby ABI. For anything other than the simplest of deployments, Mason should likely not be used to manage the Ruby LSP or any Ruby IDE tooling.
vinistock
approved these changes
Nov 19, 2024
There was a problem hiding this comment.
Thanks for your contribution!
Yeah, if Mason overrides gem installation paths without considering the Ruby version, then ABI compatibility issues are going to be very common.
And since there's so much variety with version managers, I can imagine it's easy to get into other sorts of trouble as well
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using Mason to manage Ruby LSP, unless only a single Ruby version is used, there are chances of strange errors due to conflicts of the Ruby ABI.
For anything other than the simplest of deployments, Mason should likely not be used to manage the Ruby LSP or any Ruby IDE tooling.