-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Give better error when previous installation folder is insecure to remove #7030
Merged
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
deivid-rodriguez
force-pushed
the
better-parallel-install-errors
branch
from
October 3, 2023 15:48
594d9f7
to
6de4161
Compare
martinemde
reviewed
Oct 7, 2023
Just a note that this and #6374 define exit status 37. Whichever merges first, the other needs an update (probably bundler checksums, but mentioning just in case so we don't forget.) |
It's a `BundlerError`.
deivid-rodriguez
force-pushed
the
better-parallel-install-errors
branch
from
October 27, 2023 19:55
6de4161
to
e41156e
Compare
martinemde
approved these changes
Oct 28, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that's a nice looking message, haha ;)
I see you got the exit status code too. Looks good!
deivid-rodriguez
pushed a commit
that referenced
this pull request
Nov 8, 2023
(cherry picked from commit a5f8835)
deivid-rodriguez
pushed a commit
that referenced
this pull request
Nov 8, 2023
(cherry picked from commit a5f8835)
deivid-rodriguez
pushed a commit
that referenced
this pull request
Nov 8, 2023
(cherry picked from commit a5f8835)
deivid-rodriguez
pushed a commit
that referenced
this pull request
Nov 8, 2023
(cherry picked from commit a5f8835)
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.
What was the end-user or developer problem that led to this PR?
In #6460, user was getting a Bundler error due to the previous gem installation folder having insecure permissions.
However, and even if we've lately improved the message, it's still too verbose and real culprit is a bit hidden.
What is your fix for the problem, implemented in this PR?
This error is about insecure permissions of the parent install folder for a gem, so it's independent of the particular gem that it's being uninstalled. Hence, even if you're running 8 installation jobs in parallel, the error should be displayed just once.
So my fix is to create a special error class for this that goes straight to the user, instead of being reported once per installation job.
Before
After
Make sure the following tasks are checked