Percent-encode object names in ContextUnlock #20
Conversation
This file contains 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.
At present,
gcslockpercent-encodes object names when submitting requests to the Google Cloud Storage API to create new lockfiles. However, it does not apply the same percent-encoding when issuingDELETErequests to release locks.As a result, when a new mutex is created with an object name containing a
/character (to specify a subdirectory in which the lockfiles will be held),gcslockis able to create the lockfile within the subdirectory but not delete it.This PR
url.PathEscapes object names inContextUnlockto ensure that objects created byContextLockwithin a subdirectory can be found and deleted byContextUnlock.