Closed
Conversation
4 tasks
9918754 to
7fed326
Compare
Contributor
Author
|
The error from https://travis-ci.org/apache/libcloud/jobs/160522709 seems to be a flaky installation error whereas the error from https://travis-ci.org/apache/libcloud/jobs/160522727: Appears to be a pylint error. The variable being referred to is an Element, not a unicode, object: Compare the last commit's build with the build I ran against my fork and notice that only the pylint error shows up: https://travis-ci.org/relaxdiego/libcloud/builds/160750260 |
This was referenced Sep 19, 2016
Contributor
|
fixed build in downstream PR, waiting for @relaxdiego to merge into this PR. |
asfgit
pushed a commit
that referenced
this pull request
Sep 20, 2016
asfgit
pushed a commit
that referenced
this pull request
Jan 29, 2018
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.
Description
This replaces PR #781.
Currently if a backup doesn't exists on a target, we return None, since we're using this value in getting a backup target we end up throwing an error
Also after linting, it looks like paginated responses were erroring out if paginated responses were empty.
Status
ready for review
Checklist (tick everything that applies)