Improve install advice when some gems are not found #7265
Merged
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?
This problem is quite specific to our dev environment, but I guess the fix could be handy for other situations.
After merging a change to treat default gems as regular gems, I get this when trying to run
rubocop
on our repo:However, when running the suggested command, nothing changes and I still get the same error:
The problem is that our
bin/rubocop
script uses the development version of Bundler (which has the change causing the problem), but the advice recommands the default version of Bundler, which does not yet have the change.What is your fix for the problem, implemented in this PR?
This commit changes the advice to recommend to use the same version of Bundler that run into the problem in the first place.
So in the above situation you now get:
And running that fixes the problem:
Make sure the following tasks are checked