Uh oh!
There was an error while loading. Please reload this page.
cluster: expose result of send() - #6998
Conversation
cjihrig
commented
May 26, 2016
Kind of refs: nodejs/node-v0.x-archive#8746 |
jasnell
commented
May 26, 2016
LGTM but semver-minor? |
cjihrig
commented
May 26, 2016
Definitely not semver-minor. The publicly exposed use is already documented as returning a Boolean, even though it doesn't prior to this commit. I'd say semver patch. |
jasnell
commented
May 26, 2016
Ok, works for me |
ronkorving
commented
May 27, 2016
LGTM |
CI: https://ci.nodejs.org/job/node-test-pull-request/2818/ EDIT: A few |
bnoordhuis
commented
May 28, 2016
LGTM |
CI again: https://ci.nodejs.org/job/node-test-pull-request/2841/ One more now that the CI seems healthy: https://ci.nodejs.org/job/node-test-pull-request/2873/ |
There are several places in the cluster module where a version of process.send() is called, but the result is swallowed. Most of these cases are internal, but Worker.prototype.send(), which is publicly documented, also suffers from this problem. This commit exposes the return value to facilitate better error handling, and bring Worker.prototype.send() into compliance with the documentation. PR-URL: nodejs#6998 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ron Korving <ron@ronkorving.nl> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
There are several places in the cluster module where a version of process.send() is called, but the result is swallowed. Most of these cases are internal, but Worker.prototype.send(), which is publicly documented, also suffers from this problem. This commit exposes the return value to facilitate better error handling, and bring Worker.prototype.send() into compliance with the documentation. PR-URL: #6998 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ron Korving <ron@ronkorving.nl> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
There are several places in the cluster module where a version of process.send() is called, but the result is swallowed. Most of these cases are internal, but Worker.prototype.send(), which is publicly documented, also suffers from this problem. This commit exposes the return value to facilitate better error handling, and bring Worker.prototype.send() into compliance with the documentation. PR-URL: #6998 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ron Korving <ron@ronkorving.nl> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
MylesBorins
commented
Jul 11, 2016
@cjihrig lts? |
cjihrig
commented
Jul 11, 2016
Yes, please. The v4 documentation also says that a |
MylesBorins
commented
Jul 11, 2016
Getting an error with this one |
cjihrig
commented
Jul 12, 2016
Ah, looks like this depends on #3516, which appears to have been dropped from LTS consideration. |
There are several places in the cluster module where a version of process.send() is called, but the result is swallowed. Most of these cases are internal, but Worker.prototype.send(), which is publicly documented, also suffers from this problem. This commit exposes the return value to facilitate better error handling, and bring Worker.prototype.send() into compliance with the documentation. PR-URL: nodejs#6998 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ron Korving <ron@ronkorving.nl> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Checklist
Affected core subsystem(s)
cluster
Description of change
There are several places in the
clustermodule where a version ofprocess.send()is called, but the result is swallowed. Most of these cases are internal, butWorker.prototype.send(), which is publicly documented, also suffers from this problem. This commit exposes the return value to facilitate better error handling, and bringWorker.prototype.send()into compliance with the documentation.