-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for parsing log entries w/ 'protoPayload' from resources #1578
Add support for parsing log entries w/ 'protoPayload' from resources #1578
Conversation
See: | ||
https://cloud.google.com/logging/docs/api/ref_v2beta1/rest/v2beta1/LogEntry | ||
""" | ||
_PAYLOAD_KEY = 'protoPayload' |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
I take it this hasn't been rebased yet? |
For testing code, I disagree: "it takes as much as it takes" to cover the MUT, and the arbitrary restriction on testcase method length tends to lead to "getting fancy" in testing code. |
It is current with the tip of the |
RE: Rebased, the "Add 'Logger.list_entries'." commit must not have merged cleanly then. Maybe you want to cherry-pick the last two commits? |
Github seems confused: e4b4b0d is already present on the |
Try a bit more to unconfuse it? Maybe re-fetch the remote locally? |
How? The histories look identical to me:
|
Looks like you've sorted it out. Only two commits now in this PR. |
I just tried a new |
It's not hard to argue that code like the lint-disabled |
We can't feasibly allow writing such entries until we have an answer for
@dhermes 7c52009 drops suppressing the project-wide 'too-many-statements' check for test code, and instead disables it locally for the one newly-added test: looking at it, I don't see any reason to break it up. PTAL |
Only real pending issue is my comment about seeing an example of a proto payload from a real API request. Have you been able to produce one? |
From the "Try It" form:
returns:
|
Really helpful! Thanks |
LGTM (though I still think reducing the test boilerplate for the do-nothing subclasses would be a net positive) |
@dhermes I changed |
SGTM thanks |
Add support for parsing log entries w/ 'protoPayload' from resources
Uses #1574 as a base.
Note that we can't feasibly allow writing such entries until we have an answer for #1577.