-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm_config_loglevel env variable is silencing too much (--silent) #2705
Comments
I respectfully disagree. Disrespect for this key property means a flood of literally millions of lines of useless logfile output in a container deploy scenario:
I would paste the entire buffer, but I don't think the megabytes of data are valuable — do you? In fact, you might rightfully surmise that it goes a long way toward obscuring actually useful log information by spamming log files with worthless garbage data, obliterating terminal scrollback buffers, and so on. If you want to To wit: Nobody is silencing output because they are waiting on baited breath for how long the process is going to take. |
@isolationism I understand your frustration, the idea here is to print the 6 lines of output when the log level is set to silent. We already try to do this in CI and when no tty, but clearly there are bugs there. and I'm not sure why we haven't fixed the 1000's of lines of output when we detect a tty, I believe there is a PR for it |
I am fine with download progress messages, but I think we are silencing important stuff that user is asking for:
|
The code for this is done in cypress-io/cypress#6909, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Bug
introduced by #817
Current:
npm_config_loglevel
is able to silent the stdout fromcypress version
,cypress cache list
, cypress downloading message, etcDesired:
presence of
npm_config_loglevel
should not silence important messages such as the downloading message, and output fromcypress version
andcypress cache list
, etcThe text was updated successfully, but these errors were encountered: