You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is, but require 'bundler/setup' now sets BUNDLE_LOCKFILE explicitly in the shims. Then, when BundlerManager initializes the environment and sets BUNDLE_GEMFILE to prefix/gems/Gemfile, we end up with one pointing to the user Gemfile and the other to the internal lock file.
To make matters even worse, if we only set BUNDLE_LOCKFILE in BundlerManager#initialize_environment and not in the shims, when you source env.sh you will have BUNDLE_LOCKFILE pointing to the user's lock file and BUNDLE_GEMFILE pointing to the internal gem file (set in the shim) which will cause bundler to refuse to load completely due to missing gems in the lock file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is also required on Bundler 4.0.4+