| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
I agree that it is unexpected. It looks like this was the behavior going all the way back to at least 0.12.0. The tests referenced in this PR are all newer than that, so I'm not sure that the two things are related. @bnoordhuis or @sam-github do either of you know why the inputs were originally attached to the output? |
Sorry, something went wrong.
There was a problem hiding this comment.
tiny nit: common.isWindows...
Sorry, something went wrong.
There was a problem hiding this comment.
I don't think it really matters much since we're already explicitly passing 'win32' to this function below here.
Sorry, something went wrong.
|
Forgot to re-add a removed test. New CI: https://ci.nodejs.org/job/node-test-pull-request/8594/ |
Sorry, something went wrong.
|
/cc @nodejs/ctc |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Sorry, something went wrong.
|
Sorry, I don't know why they were added. Getting rid of them seems like a good idea. |
Sorry, something went wrong.
CITGM clean |
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: nodejs#13601 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
In PR [1], a bunch of properties were removed from the error thrown by execSync and execFileSync. It turns out that some of those were still supposed to be there, as the documentation states that the error contains the entire result from the spawnSync call. [1] nodejs#13601
In PR [1], a bunch of properties were removed from the error thrown by execSync and execFileSync. It turns out that some of those were still supposed to be there, as the documentation states that the error contains the entire result from the spawnSync call. [1] #13601 PR-URL: #16060 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
In PR [1], a bunch of properties were removed from the error thrown by execSync and execFileSync. It turns out that some of those were still supposed to be there, as the documentation states that the error contains the entire result from the spawnSync call. [1] nodejs/node#13601 PR-URL: nodejs/node#16060 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
In PR [1], a bunch of properties were removed from the error thrown by execSync and execFileSync. It turns out that some of those were still supposed to be there, as the documentation states that the error contains the entire result from the spawnSync call. [1] nodejs/node#13601 PR-URL: nodejs/node#16060 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
| Back | FazBrowse Home | New Git URL |
It appears that when the synchronous child_process methods were added, additional information such as user-provided/parsed options, etc. was being copied to the returned object. Not only is this undocumented/unexpected, but it looks like this may have only been done for the purposes of tests (to test normalized/default options for example).
This PR extracts the actual sync spawning into an internal function which can then be monkey-patched as needed by tests.
I have also changed the errors returned by the exec*Sync() methods so that it matches that of the Error object mutation done for the async exec*() methods (e.g. err.result contains the libuv error name for status codes less than 0).
CI: https://ci.nodejs.org/job/node-test-pull-request/8593/
Checklist
Affected core subsystem(s)