CORE: change log level of config_modify #667
Merged
Conversation
This file contains 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
Sergei-Lebedev
force-pushed
the
topic/context_modify_log_level
branch
from
4961424 to
ab6dbaa
Compare
manjugv
approved these changes
Nov 9, 2022
vspetrov
approved these changes
Nov 13, 2022
Sergei-Lebedev
force-pushed
the
topic/context_modify_log_level
branch
from
ab6dbaa to
3777726
Compare
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.
What
Change log level of ucc_context_config_modify to INFO when CL or TL is not found
Why ?
User might not know in advance what TL or CL are loaded in runtime. Instead of printing just return UCC_ERR_NOT_FOUND