Make lockfiles opt-in instead of defaulting to on. #74
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR addresses issues introduced by locking in the previous release by making locking Opt-In. Set the environment variable
CPENV_ENABLE_LOCKFILESto 1 to enable lockfiles and ensure that only 1 process on a given machine can localize a module at a time.There seems to have been issues of file-ownership on machines with multiple users where one user could create a lock while localizing a module, and later another user would be unable to activate the same module.
Fixes #73
Autocpenv and tk-cpenv will be updated shortly.