Fixes the delete object issue for docker environment #144
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
ebozduman
force-pushed
the
delete_obj_fails_for_docker
branch
from
08d9900
to
4fe6f0c
Compare
. Adds more verbosity to cleanup exception messages . Removes the forgotten debug message
ebozduman
force-pushed
the
delete_obj_fails_for_docker
branch
from
00eb950
to
4d4bb29
Compare
|
@ebozduman , there is a travis failure. |
This was referenced Sep 22, 2017
Closed
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.
Fixes issue #142
After new AWS Ruby SDK version 3 is made available recently last month, argument for object/file delete api is modified. That was the cause of the problem, which means there is a backward compatibility issue between previous version of AWS Ruby SDK and the latest version.