Feature Request - Log non-error messages to stdout instead of stderr
Reported by
br...@dockyard.com,
Oct 30 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36 Steps to reproduce the problem: 1. View the level of any output 2. 3. What is the expected behavior? I would expect any non-error output to be sent to stdout instead of stderr. I originally opened this as a bug in https://bugs.chromium.org/p/chromium/issues/detail?id=773572&can=1&q=stderr&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified but we directed to open this as a formal feature request for all of Chromium. I hope this is the correct place to do so! What went wrong? All messages regardless of their intent are sent to stderr. This makes handling the output from chrome very difficult. At the moment we have to parse the output to understand what the intent is and if an error actually did occur. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 62.0.3202.62 Channel: n/a OS Version: OS X 10.12.6 Flash Version:
,
Oct 30 2017
This seems to be a feature request. Hence, marking it as untriaged for further inputs from dev team. Thanks...!!
,
Oct 30 2017
,
Oct 30 2017
stdout is meant for the regular output of a program, and since Chromium is a GUI application, it doesn't really have any text-based output (as opposed to CLI programs like echo, cat, ls, etc. that do write output to stdout). stderr is for log messages and diagnostic information, which is why Chromium writes logs there. This really shouldn't cause issues; in the other bug you linked, you can just not redirect stderro to /dev/null, or you can redirect stderr to stdout.
,
Oct 30 2017
> stdout is meant for the regular output of a program, and since Chromium is a GUI application, it doesn't really have any text-based output with headless this is no longer the case. The headless team has said they need to keep the same output level as chromium so this decision in chromium is affecting that effort |
||||
►
Sign in to add a comment |
||||
Comment 1 by phistuck@chromium.org
, Oct 30 2017