bundle viz
fails with NoMethodError
#3217
Comments
Not super sure, no. It seems like you somehow have a dependency that's nil, but I'm not sure how that would happen. Can you follow ISSUES and report back? |
Whole |
I have exactly the same error. |
Reproducable with @hauleth 's gemfile with RubyGems 2.4.4. RubyGems 2.2.2 works fine with the same Gemfile. Gemfile generated by minimal Gemfile to reproduce:
investigating deeper... |
It is caused by |
Previously RubyGems would activate prerelease gems with Kernel#gem. This behavior was undefined and wrong as use of prerelease gems should always be explicitly opt-in. Now you must specify prerelease requirements to use prerelease gems. Fixes #938
I have this issue. I'm not quite sure I follow why this is happening, but is there a reliable workaround? |
@aprescott Can you fill an issue with the recommended format ? It is the easiest way to have all requirements to reproduce it and possibly fix it. Edit: If by any chance you are using rails |
My issue is basically exactly as described here, with potentially different versions. ruby 2.2.2p95, rubygems 2.4.6, bundler 1.9.5, rails 4.2.1. I can open another issue, though, if the duplication is fine. (I'd just be linking to this issue anyway.) |
The file https://github.com/bundler/bundler/blob/master/ISSUES.md has specific instructions for what we need to know in order to try to reproduce your problem. Please read the file and follow the instructions.
|
Apologies for the noise. I dug into this some more and I can't provide more than what you already know with the commit linked in this issue. It's a similar problem with an |
I believe this is fixed now and can be closed. |
just for the record and it may help someone. I had this output:
After upgrading to bundler 1.10.5, the problem was gone and the graphic was created. Cheers Andy |
After running
bundle viz
I get this:Any idea what is wrong?
The text was updated successfully, but these errors were encountered: