Don't load more specs after the whole set of specs has been setup #4262
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?
If bundler is being used, and spec is not included in the bundle,
Gem::Specification.find_by_name
will still leak outside of the bundle and find globally installed specs.What is your fix for the problem, implemented in this PR?
This is a regression of #2711.
The lazy loading provided by that PR when the whole set of
@@stubs
is not yet set is still interesting, so I kept that but restored the old behaviour of not trying to load anything else once@@stubs
have been set.Fixes #4253.
Make sure the following tasks are checked