Fixing credentials without scopes issue in logging. #2934
Merged
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
See: https://travis-ci.org/GoogleCloudPlatform/google-cloud-python/builds/191433056#L2195 This is a band-aid for now. I caused it in googleapis#2875 and will roll-back this roll-back at a later time. @daspecter fixed a similar breakage in googleapis#2909.
googlebot
added
the
cla: yes
dhermes
added
api: logging
daspecster
approved these changes
Jan 12, 2017
|
Travis is just finishing up, but it LGTM. |
19 tasks
richkadel
pushed a commit
to richkadel/google-cloud-python
that referenced
this pull request
May 6, 2017
Fixing credentials without scopes issue in logging.
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.
See:
https://travis-ci.org/GoogleCloudPlatform/google-cloud-python/builds/191433056#L2195
This is a band-aid for now. I caused it in #2875 and will roll-back this roll-back at a later time.
@daspecster fixed a similar breakage in #2909.