-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
uninitialized constant Bundler #12848
Comments
@koic @amomchilov This issue refuses to go away! 😅 |
Fixes rubocop#12848. This PR fixes an error that occurs in `RuboCop::Lockfile` when the constant Bundler is uninitialized.
Thanks for the quick turn around on a PR. May I ask why this route was chosen instead of putting in the code to require bundler? |
Exactly, but the existence of |
Fixes #12848. This PR fixes an error that occurs in `RuboCop::Lockfile` when the constant Bundler is uninitialized.
I'm getting the error
uninitialized constant Bundler
in my rubocop runs with rubocop.This appears to only happen when using rubocop-rails and rubocop is called from outside of
bundle exec
.Expected behavior
Rubocop should run without a backtrace
Actual behavior
Steps to reproduce the problem
I ran these commands in a fresh container using the
ruby:3.1
docker imageRuboCop version
The text was updated successfully, but these errors were encountered: