-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
report: list envvars using uv_os_environ() #28963
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
the
lib / src
Issues and PRs related to general changes in the lib or src directory.
label
Aug 5, 2019
saghul
approved these changes
Aug 5, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
gengjiawen
approved these changes
Aug 5, 2019
addaleax
approved these changes
Aug 5, 2019
cjihrig
force-pushed
the
envvars
branch
3 times, most recently
from
August 11, 2019 15:35
8b89159
to
097a154
Compare
cjihrig
added
report
Issues and PRs related to process.report.
and removed
blocked
PRs that are blocked by other issues or PRs.
lib / src
Issues and PRs related to general changes in the lib or src directory.
labels
Aug 11, 2019
CI: https://ci.nodejs.org/job/node-test-pull-request/24939/ EDIT: CI was yellow. |
This commit simplifies the diagnostic report's code for listing environment variables by using uv_os_environ() instead of platform specific code. PR-URL: nodejs#28963 Reviewed-By: Saúl Ibarra Corretgé <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
targos
pushed a commit
that referenced
this pull request
Aug 19, 2019
This commit simplifies the diagnostic report's code for listing environment variables by using uv_os_environ() instead of platform specific code. PR-URL: #28963 Reviewed-By: Saúl Ibarra Corretgé <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
This was referenced Aug 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: This PR is a bit premature. It requires the libuv 1.31.0 update, which will happen later this week. Only the second commit (report: list envvars using uv_os_environ()
) is relevant. libuv 1.31.0 includes a new API,uv_os_environ()
, for iterating over the environment variables.This PR simplifies the diagnostic report's code for listing environment variables by using
uv_os_environ()
instead of platform specific code.cc: @nodejs/libuv
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes