Skip to content
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

(v6.x backport) process: add --redirect-warnings command line argument #14418

Merged

Conversation

sam-github
Copy link
Contributor

The --redirect-warnings command line argument allows process warnings
to be written to a specified file rather than printed to stderr.

Also adds an equivalent NODE_REDIRECT_WARNINGS environment variable.

If the specified file cannot be opened or written to for any reason,
the argument is ignored and the warning is printed to stderr.

If the file already exists, it will be appended to.

PR-URL: #10116
Reviewed-By: Michael Dawson [email protected]
Reviewed-By: Michal Zasso [email protected]
Reviewed-By: Fedor Indutny [email protected]

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. process Issues and PRs related to the process subsystem. v6.x labels Jul 21, 2017
@sam-github
Copy link
Contributor Author

backport of 03e89b3 from #10116

@jasnell jasnell added the semver-minor PRs that contain new features and should be released in the next minor version. label Jul 21, 2017
The --redirect-warnings command line argument allows process warnings
to be written to a specified file rather than printed to stderr.

Also adds an equivalent NODE_REDIRECT_WARNINGS environment variable.

If the specified file cannot be opened or written to for any reason,
the argument is ignored and the warning is printed to stderr.

If the file already exists, it will be appended to.

PR-URL: nodejs#10116
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Michal Zasso <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
@sam-github sam-github force-pushed the v6.x-backport-redirect-warnings branch from da1f2b3 to a879dc8 Compare July 24, 2017 17:30
@sam-github sam-github merged commit a879dc8 into nodejs:v6.x-staging Jul 24, 2017
sam-github pushed a commit that referenced this pull request Jul 24, 2017
The --redirect-warnings command line argument allows process warnings
to be written to a specified file rather than printed to stderr.

Also adds an equivalent NODE_REDIRECT_WARNINGS environment variable.

If the specified file cannot be opened or written to for any reason,
the argument is ignored and the warning is printed to stderr.

If the file already exists, it will be appended to.

Backport-PR-URL: #14418
PR-URL: #10116
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Michal Zasso <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
@sam-github sam-github deleted the v6.x-backport-redirect-warnings branch July 24, 2017 17:36
@sam-github
Copy link
Contributor Author

@nodejs/lts I think I landed this on v6.x-staging in error, looking at https://github.com/nodejs/LTS/wiki#q4-2017-boron-6x-release-schedule, we are only planning a minor every 4 months? At least, its 4 months from the June 6 release of 6.11.0 and the Nov 7th planned release of 6.12.0. I misremembered the cadence as being a release a month, with every other month being a minor.

I guess I should back it out and restore the branch?

@gibfahn
Copy link
Member

gibfahn commented Jul 25, 2017

@MylesBorins did this go into the rc? If so it'd probably be better for Myles to back it out (so he knows what's going on).

I'm a little surprised by the delay until the next minor, 4 months seems a little excessive. Maybe open an issue in lts and we can discuss at the next meeting.

@MylesBorins
Copy link
Contributor

Please back this out, it has not been included in the latest RC

We can do a minor next month if we want. I documented the options in the release schedule found in the wiki

@sam-github sam-github restored the v6.x-backport-redirect-warnings branch July 25, 2017 15:33
@sam-github
Copy link
Contributor Author

Popped this off of v6.x-staging, re-PRed.

Jeyanthinath pushed a commit to Jeyanthinath/node that referenced this pull request Jul 26, 2017
The --redirect-warnings command line argument allows process warnings
to be written to a specified file rather than printed to stderr.

Also adds an equivalent NODE_REDIRECT_WARNINGS environment variable.

If the specified file cannot be opened or written to for any reason,
the argument is ignored and the warning is printed to stderr.

If the file already exists, it will be appended to.

Backport-PR-URL: nodejs#14418
PR-URL: nodejs#10116
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Michal Zasso <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c++ Issues and PRs that require attention from people who are familiar with C++. process Issues and PRs related to the process subsystem. semver-minor PRs that contain new features and should be released in the next minor version.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants