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
Add Bundler.with_unbundled_env
to RSpec.shared_context 'isolated environment'
#12612
base: master
Are you sure you want to change the base?
Add Bundler.with_unbundled_env
to RSpec.shared_context 'isolated environment'
#12612
Conversation
…nvironment'` It's more correct. And without it there are errors, like about `yard` gem: ``` > bundle exec rspec ... /home/alex/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/definition.rb:570:in `materialize': Could not find yard-0.9.34 in locally installed gems (Bundler::GemNotFound) from /home/alex/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/definition.rb:203:in `specs' from /home/alex/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/definition.rb:270:in `specs_for' ... ``` There are some incompatibilities, but they can be resolved.
create_empty_file('Gemfile') | ||
create_empty_file('Gemfile.lock') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without this CLI returns "can't open file Gemfile.lock
", I don't know why.
before do | ||
# Makes sure the project dir of rubocop server is the isolated_environment | ||
create_empty_file('Gemfile') | ||
end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to move create_empty_file('Gemfile')
into "isolated environment", but it breaks more than helps.
Please, help me with this, I don't understand:
|
And I see fails from |
It's more correct. And without it there are errors, like about
yard
gem:There are some incompatibilities, but they can be resolved.
Basically, I couldn't run specs from "the cold start".
Before submitting the PR make sure the following are checked:
[Fix #issue-number]
(if the related issue exists).master
(if not - rebase it).bundle exec rake default
. It executes all tests and runs RuboCop on its own code.{change_type}_{change_description}.md
if the new code introduces user-observable changes. See changelog entry format for details.