Return a useful error for etcd Lock when aborting the Lock operation instead of nil, nil #64
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
…instead of nil, nil Signed-off-by: Alexandre Beslic <abronan@docker.com>
|
LGTM |
abronan
added a commit
that referenced
this pull request
Sep 24, 2015
Return a useful error for etcd Lock when aborting the Lock operation instead of nil, nil
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.
Not aligned with other backends (Consul client handles the stop chan directly and zookeeper does not take any stop chan), but kind of feels horrible to return
nil, nilin this one...Signed-off-by: Alexandre Beslic abronan@docker.com