-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Uninitialized constant Bundler::Plugin::API::Source. #5409
Comments
We really need a test case that reproduces this, since I can't reproduce it on any of the ruby apps I have lying around |
Experiencing the same issue on a rails app using rubygems 2.4.8 and bundler 1.14.3 |
I have just updated my rubygems to 2.6.10 and the issue is gone fyi. |
ping @dekellum Are you still experiencing your reported issue? |
Yes: https://travis-ci.org/dekellum/syncwrap/jobs/203321757#L208 It seems impossible to test this in Bundler's test environment. My only guess here is that there is something recursive going on with use of auto-load in bundler that isn't working well. See also #4981. |
@dekellum that example is limited to Bundler 1.13.x, which does not contain the fix. Please try again with Bundler 1.14.x and report back. |
That failing build was in fact using bundler 1.14.4: https://travis-ci.org/dekellum/syncwrap/jobs/203321757#L195 But it did confusingly contain an incomplete attempt to workaround via bundler 1.13.x. Here is a pristine .travis.yml and a freshly failing build also using bundler 1.14.4: |
@dekellum can you please update Ruby Gems to the latest version in travis. |
@colby-swandale, are just asking me to do that in order to further probe the possible cause of the problem? I can add that change on another disposable branch. Can you point me at a .travis.yml recipe for rubygems update? But I have no doubt that later versions of rubygems (2.6.x, as stated in my initial report) will not exhibit this problem. Are you stating that bundler, as of 1.14.4 at least, is dropping support for this older version of rubygems? I have no idea why the Travis environment is defaulting to this problem combination of the newest version of Bundler and this old version of Rubygems. A stock ruby 2.2.6p396 (version I'm testing) includes rubygems 2.4.5.2. Not sure if its RVM that is changing it to 2.4.8 or if the stock version has later backported fixes? |
So I just confirmed: I can reproduce this on both (ruby 2.2.6 stock) rubygems 2.4.5.2 and (Travis/RVMs) rubygems 2.4.8. |
@dekellum thank you for checking! Is there anything you can tell us that would help us figure out how to reproduce this issue outside of a Travis build environment? We'd like to fix it, but it's very hard to know if we have without a reliable reproduction case to test against. |
@dekellum I couldn't reproduce that failure locally using rubygems 2.4.8 and ruby 2.2.4, I'll try downloading 2.2.6 when I get to better internet |
I was able to reproduce it in my local dev environment with stock ruby 2.2.6, rubygems 2.4.5.2, once I removed all traces of a prior rubygems-update. The travis build gives good detail on repro. steps. |
Here is warnings, stack trace via
No such warning or stack trace with rubygems 2.6.10. |
This appears to be another viable workaround, suggesting that the auto-loads are not behaving as intended. github: rubygems/bundler#5409
A simple require as in dekellum/syncwrap@cd5df2a is also a valid workaround: |
Thanks for the stack trace for the circular require -- I think that gives me enough information to fix the bug! |
…efined, r=indirect Avoid undefined Bundler::Plugin::API::Source exception Fixes #5409, with a test!
I saw somewhere who has shared what they did, and I couldn't find that. I am sharing it again here:
This worked for me using with the change from #5459 Thanks 😃 |
Thanks @imechemi! This fixed it for me. |
Seems this issue has reappeared in bundler 1.14.x in combination with 2.4.x rubygems. See:
https://travis-ci.org/dekellum/syncwrap/jobs/197069321#L202
Its not an issue with either rubygems 2.6.x (2.6.6 in one env.), or with bundler 1.13.7 as I'm able to demonstrate here:
https://travis-ci.org/dekellum/syncwrap/jobs/197079264
I think this is very similar to reports and PR #4981.
If the rake project can reproduce the issue, we don't know via travis, given that its pegged to bundler 1.13.x:
https://github.com/ruby/rake/blob/34f5e2e27d2c49431b7c84d0787eaf6afcddf794/.travis.yml
Cc: @hsbt
But here are some other reports of this with bundler 1.14.3:
The text was updated successfully, but these errors were encountered: