You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could also be considered a CR/FR but as it causes unexpected behaviour for software packaged with box, I rather think of it as a bug. The program arises when the program being packaged with box writes structured output (e.g. json) to stdout and its corresponding (debug-)logs to stderr. Activating debug-level logging via -vvv for the packaged program now breaks the json-output as the box-logs are also printed on stdout.
As the output of the requirements checker is rather diagnostic then conversational (see: https://pubs.opengroup.org/onlinepubs/9699919799/functions/stderr.html), I would expect to have that output on stderr.
For discussions around using stdout/stderr for logging:
Bug report
This could also be considered a CR/FR but as it causes unexpected behaviour for software packaged with box, I rather think of it as a bug. The program arises when the program being packaged with box writes structured output (e.g. json) to stdout and its corresponding (debug-)logs to stderr. Activating debug-level logging via
-vvv
for the packaged program now breaks the json-output as the box-logs are also printed on stdout.As the output of the requirements checker is rather diagnostic then conversational (see: https://pubs.opengroup.org/onlinepubs/9699919799/functions/stderr.html), I would expect to have that output on stderr.
For discussions around using stdout/stderr for logging:
IMO this should be resolved by just switching the stream here but in case this is considered a BC, it should at least become configurable somehow.
The text was updated successfully, but these errors were encountered: