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

Warn on unresolved specs #56

Merged
merged 1 commit into from
May 11, 2019
Merged

Conversation

lamont-granquist
Copy link
Contributor

These produce horrible perf degredation in rubygems internally:

rubygems/rubygems#2761

Due to appbundler this "should" not happen, but due to:

f01aea0

And due to ruby now shipping with bundler, we were getting two versions
of bundler and an unresolved spec, and therefore rubygems had
significant performance issues. All that is required is correctly
activating bundler in the appbundler binstub and the spec becomes
resolved and the perf issues go away.

This commit just adds some warning about the issue so that people report
it, with a clear bit of text to not just ignore it.

These produce horrible perf degredation in rubygems internally:

rubygems/rubygems#2761

Due to appbundler this "should" not happen, but due to:

f01aea0

And due to ruby now shipping with bundler, we were getting two versions
of bundler and an unresolved spec, and therefore rubygems had
significant performance issues.  All that is required is correctly
activating bundler in the appbundler binstub and the spec becomes
resolved and the perf issues go away.

This commit just adds some warning about the issue so that people report
it, with a clear bit of text to not just ignore it.

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
@lamont-granquist lamont-granquist merged commit 3a8301e into master May 11, 2019
@lamont-granquist lamont-granquist deleted the lcg/warn-on-unresolved-spec branch May 11, 2019 00:26
@@ -330,6 +330,11 @@ def load_statement_for(bin_file)
spec = Gem::Specification.find_by_name("#{name}")
end

unless Gem::Specification.unresolved_deps.empty?
$stderr.puts "APPBUNDLER WARNING: unresolved deps are CRITICAL performance bug, this MUST be fixed"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are a?

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