-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
cluster: expose result of send() #6998
Conversation
Kind of refs: nodejs/node-v0.x-archive#8746 |
LGTM but semver-minor? |
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. |
Ok, works for me |
LGTM |
CI: https://ci.nodejs.org/job/node-test-pull-request/2818/ EDIT: A few |
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 <[email protected]> Reviewed-By: Ron Korving <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
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 <[email protected]> Reviewed-By: Ron Korving <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
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 <[email protected]> Reviewed-By: Ron Korving <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
@cjihrig lts? |
Yes, please. The v4 documentation also says that a |
Getting an error with this one
|
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 <[email protected]> Reviewed-By: Ron Korving <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Checklist
Affected core subsystem(s)
cluster
Description of change
There are several places in the
cluster
module 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.