Works for CONAN_LOG_LEVEL values of quiet, error, warning, notice, status, verbose, v, debug, vv, and trace.
This is in line with the -v options of conan config.
However, "unsetting" the CONAN_LOG_LEVEL variable by export CONAN_LOG_LEVEL= or running
CONAN_LOG_LEVEL= conan config home
result in the error message
ERROR: Invalid argument '-v'
Similarly, specifying some random value for CONAN_LOG_LEVEL will still refer to the invalid argument -v<randomvalue>.
This is confusing behavior, since we don't explicitly specify -v on the command line. It is even more confusing for the case of setting CONAN_LOG_LEVEL= to an empty value (using unset CONAN_LOG_LEVEL works).
Change in behavior
a) Check the value for CONAN_LOG_LEVEL before passing its value as an argument further, and print a more informative error message.
b) Allow unsetting with export CONAN_LOG_LEVEL=
What is your suggestion?
Used version 2.9.1.
Observation
Works for
CONAN_LOG_LEVEL
values ofquiet
,error
,warning
,notice
,status
,verbose
,v
,debug
,vv
, andtrace
. This is in line with the-v
options ofconan config
.However, "unsetting" the
CONAN_LOG_LEVEL
variable byexport CONAN_LOG_LEVEL=
or runningresult in the error message
Similarly, specifying some random value for
CONAN_LOG_LEVEL
will still refer to the invalid argument-v<randomvalue>
.This is confusing behavior, since we don't explicitly specify
-v
on the command line. It is even more confusing for the case of settingCONAN_LOG_LEVEL=
to an empty value (usingunset CONAN_LOG_LEVEL
works).Change in behavior
a) Check the value for
CONAN_LOG_LEVEL
before passing its value as an argument further, and print a more informative error message. b) Allow unsetting withexport CONAN_LOG_LEVEL=
Have you read the CONTRIBUTING guide?