| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Labels can be passed in explicitly to the 'log_text', 'log_struct', or 'log_proto' methods. If not passed, any default values configured on the logger instance will be used. See: #1566.
|
|
||
| labels = self._get_labels(labels) | ||
| if labels is not None: | ||
| data['entries'][0]['labels'] = labels |
It was needed earlier for batch support, but was masked by the attribute on the mock '_Logger' used by the batch tests.
| return Batch(self, client) | ||
|
|
||
| def log_text(self, text, client=None): | ||
| def _make_entry_resource(self, text=None, info=None, message=None, |
|
LGTM. 7 commits seems like a lot? |
Sorry, something went wrong.
Two of the commits are bugfixes for already-merged-to-logging-api code. :( |
Sorry, something went wrong.
|
You can do with the commits as you see fit. You are go to merge on my end. |
Sorry, something went wrong.
|
I merged as-is after aborting a rebase where I tried to clean it up. |
Sorry, something went wrong.
* fix: mock return_value should not populate oneof message fields
…nt (#1668) skip failing samples due to public access prevention enforcement. More Details on b/469643064
| Back | FazBrowse Home | New Git URL |
Fetched entries expose labels set on the back-end.
When logging, labels can be passed in explicitly to the log_text, log_struct, or log_proto methods. If not passed, any default values configured on the logger instance will be used.
See: #1566.