| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Can you at least line these two lines up with chunk? Same for the other instance of this below.
Sorry, something went wrong.
There was a problem hiding this comment.
Aligned.
Sorry, something went wrong.
Sorry, something went wrong.
|
Looks like the common.mustCall(..., 2) will have to be changed to just common.mustCall() an "at least twice" check or even better, ensure that each separate callback is called at least once, for the stdout-stderr-data test. Windows seems to be less reliable in its chunking? |
Sorry, something went wrong.
|
@mscdex Whoops, yeah, fixed, I hope, let's try again... |
Sorry, something went wrong.
|
CI looks good. /cc @bnoordhuis @cjihrig |
Sorry, something went wrong.
There was a problem hiding this comment.
Can you drop the negation and flip the clauses?
Sorry, something went wrong.
This reverts commit c9a5990.
A previous fix for a `maxBuffer` bug resulted in a change to the argument type for the `data` event on `child.stdin` and `child.stdout` when using `child_process.exec()`. This fixes the `maxBuffer` bug in a way that does not have that side effect. Fixes: nodejs#7342 Refs: nodejs#1901
|
CI again, hoping my echo for unicode characters tests work across platforms... |
Sorry, something went wrong.
|
Modified tests for Windows. Let's try again: |
Sorry, something went wrong.
|
That CI is green. Woot. @bnoordhuis I put quotation marks around process.execPath but I'm pretty sure other characters that could conceivably be in the path may adversely affect at least some platforms (probably at least some of $, backticks, different types of quotation marks and slashes, question marks, asterisk...). Maybe that's OK because those are sufficiently infrequent while spaces are pretty common? |
Sorry, something went wrong.
|
LGTM
I agree. |
Sorry, something went wrong.
|
I'll land this in 24 hours if no one objects. An additional LGTM or two would be nice, though. /cc @nodejs/collaborators |
Sorry, something went wrong.
A previous fix for a `maxBuffer` bug resulted in a change to the argument type for the `data` event on `child.stdin` and `child.stdout` when using `child_process.exec()`. This fixes the `maxBuffer` bug in a way that does not have that side effect. PR-URL: #7391 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Jackson Tian <shyvo1987@gmail.com> Fixes: #7342 Refs: #1901
|
@thealphanerd Yes if #6764 lands on LTS, otherwise no. |
Sorry, something went wrong.
|
I've gone ahead and landed this as #6764 landed. Do you think we would be better without either of these changes? Is there any chance of a regression? |
Sorry, something went wrong.
A previous fix for a `maxBuffer` bug resulted in a change to the argument type for the `data` event on `child.stdin` and `child.stdout` when using `child_process.exec()`. This fixes the `maxBuffer` bug in a way that does not have that side effect. PR-URL: #7391 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Jackson Tian <shyvo1987@gmail.com> Fixes: #7342 Refs: #1901
|
@thealphanerd I think we're better off with these changes than without them. |
Sorry, something went wrong.
A previous fix for a `maxBuffer` bug resulted in a change to the argument type for the `data` event on `child.stdin` and `child.stdout` when using `child_process.exec()`. This fixes the `maxBuffer` bug in a way that does not have that side effect. PR-URL: #7391 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Jackson Tian <shyvo1987@gmail.com> Fixes: #7342 Refs: #1901
A previous fix for a `maxBuffer` bug resulted in a change to the argument type for the `data` event on `child.stdin` and `child.stdout` when using `child_process.exec()`. This fixes the `maxBuffer` bug in a way that does not have that side effect. PR-URL: #7391 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Jackson Tian <shyvo1987@gmail.com> Fixes: #7342 Refs: #1901
A previous fix for a `maxBuffer` bug resulted in a change to the argument type for the `data` event on `child.stdin` and `child.stdout` when using `child_process.exec()`. This fixes the `maxBuffer` bug in a way that does not have that side effect. PR-URL: #7391 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Jackson Tian <shyvo1987@gmail.com> Fixes: #7342 Refs: #1901
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
child_process
Description of change
A previous fix for a maxBuffer bug resulted in a change to the
argument type for the data event on child.stdin and child.stdout
when using child_process.exec().
This fixes the maxBuffer bug in a way that does not have that side
effect.
Fixes: #7342
Refs: #1901
Alternative to #7381 (which changes the argument type and is arguably semver-major for that reason--being affected by it requires relying on undocumented behavior and using exec() in ways that are better suited to fork() or spawn() which are unaffected by either fix).