Uh oh!
There was an error while loading. Please reload this page.
Adding scope to error reporting client. - #3334
Merged
Merged
Conversation
dhermes
commented
Apr 27, 2017
ContributorAuthor
@waprin I take your merging as an affirmation that the scope I picked was correct? |
waprin
commented
Apr 27, 2017
Contributor
It's right as far as I know and the docs go. |
richkadel pushed a commit
to richkadel/google-cloud-python
that referenced
this pull request
May 6, 2017
parthea pushed a commit
that referenced
this pull request
Nov 24, 2025
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
/cc @jonparrott
Fixes#3263
FWIW I have no idea if this is the correct scope, I couldn't find one in the official docs but I just based it off the scopes in the discovery doc