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
0.2.5 fails to load from an incompatible libv8 version update #140
Comments
Hi, Could you provide the output of Why would the resolver pick the lowest version higher than 6.9.411? Should it not pick the latest version after 6.9.411? Is this some rubygems/bundler behaviour I am not aware about? @SamSaffron, do you have any hints? |
@ignisf sure thing! It's worth noting that this is happening in a Docker environment (host machine is MacOS).
And just for completeness:
|
That's my understanding, after checking Bundler's 1.17 manpage for |
In the meantime I've yanked the 7.0 versions as they were faulty anyway. |
You can now try again and see what will happen |
After looking into this some more, I think the cause is related to a Rubygems mirror caching issue. We're not actually using Apologies for what turned out to be a false bug report. Thank you for responding so quickly. |
👍 no worries |
Summary
On a
bundle update mini_racer
, 0.2.5 specifies a libv8 version requirement of>= 6.9.411
, which doesn't exist. As a result, lib8 version7.0.276.38.0beta1
is used (a prerelease!), which breaksrequire "mini_racer"
, causing execjs to fail to find an available runtime.Details
I work on an application which saw a version bump from 0.2.4 to 0.2.5. Our CI build started failing when attempting to load the Rails environment:
This failure seems to happen because of a problem with
mini_racer_extension.so
:Looking at the
Gemfile.lock
diff, there are 2 changes:One thing that stands out is that
libv8
has been upgraded from a non-prerelease version to a prerelease version.A coworker noticed that libv8 version 6.9.411 isn't an available version. What I think is happening is that libv8 version 6.9.411 doesn't exist, so the dependency resolver picks the lowest version higher than 6.9.411, which is 7.0.276.38.0beta1. Unfortunately, it looks like that version isn't compatible with 0.2.5.
Discussion about pinning to 6.9 vs 7.3 seems to have happened as part of #138 (comment).
The text was updated successfully, but these errors were encountered: