This repository was archived by the owner on Jun 20, 2023. It is now read-only.
Force specific log tags in a few instances #1249
Merged
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.
Force specific logtags as automatic tag generation does not produce unique tags here (i.e. "BaseContinuationImpl").
Noticed this while reviewing some of the log files testers provided.
Mostly affects lamdas, often in relation to coroutines.
Otherwise we have a few cases where it doesn't log the obvious source: