[PlaygroundLogger] Added support for an environment variable which co… #53
Conversation
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
…ntrols the maximum depth of logging. Logging previously unconditionally used a maximum depth of 2 when using one of the regular entry points (because logging would use the default policy). This commit allows clients to set `LOGGER_DEPTH` in the environment when launching the process performing logging; if this is set to a valid integer, it will override the default depth of 2. This addresses <rdar://problem/67252287>.
cwakamo
force-pushed
the
PlaygroundLogger-override-maximum-depth-env-var
branch
from
dafb12b to
469b06e
Compare
jonathanpenn
approved these changes
Mar 3, 2021
|
This repo doesn't have Swift CI support, but I've tested this locally using the same Xcode tools that are used in Swift CI. |
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.
…ntrols the maximum depth of logging.
Logging previously unconditionally used a maximum depth of 2 when using one of the regular entry points (because logging would use the default policy).
This commit allows clients to set
LOGGER_DEPTHin the environment when launching the process performing logging; if this is set to a valid integer, it will override the default depth of 2.This addresses rdar://problem/67252287.