FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

cluster: disconnect event was not emitted correctly by Olegas · Pull Request #1386 · nodejs/node · GitHub

/ node Public

cluster: disconnect event was not emitted correctly - #1386

Closed
Olegas wants to merge 1 commit into
nodejs:v1.xfrom
Olegas:worker-emit-disconnect
Closed

cluster: disconnect event was not emitted correctly#1386
Olegas wants to merge 1 commit into
nodejs:v1.xfrom
Olegas:worker-emit-disconnect

Conversation

Olegas commented Apr 9, 2015

Copy link
Copy Markdown
Contributor

Fix for #1304
Inside of a worker, disconnect event was not emitted on cluster.worker

Fishrock123 added the cluster Issues and PRs related to the cluster subsystem. label Apr 9, 2015

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Instead of doing this, can you check out test/parallel/test-cluster-worker-death.js, and do something similar.

EDIT: Upon further review, that approach might not work. @bnoordhuis any better ideas on how to trigger an assertion in the parent process after a disconnect in the child?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Instead of creating files in __dirname, can you use common.tmpDir.

Olegas commented Apr 9, 2015

Copy link
Copy Markdown
Contributor Author

@cjihrig done

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Please add a space between ) and {

cjihrig commented Apr 9, 2015

Copy link
Copy Markdown
Contributor

One style nit. Can you address it and squash the commits. Then, I'll run it through the CI.

Fix for nodejs#1304
Inside of a worker, disconnect event was not emitted on cluster.worker
Olegas force-pushed the worker-emit-disconnect branch from fd21b92 to ded311c Compare April 9, 2015 21:54

Olegas commented Apr 9, 2015

Copy link
Copy Markdown
Contributor Author

@cjihrig done

cjihrig commented Apr 9, 2015

Copy link
Copy Markdown
Contributor

Copy link
Copy Markdown
Contributor

CI looks good. I'll merge this in the coming days, assuming there is no more activity.

Olegas commented May 5, 2015

Copy link
Copy Markdown
Contributor Author

@brendanashworth do I need to rewrite my PR to master branch?

Copy link
Copy Markdown
Contributor

No, it'll be merged manually into master anyways.

brendanashworth self-assigned this May 8, 2015
brendanashworth pushed a commit that referenced this pull request May 8, 2015
Inside of a worker, disconnect event was not emitted on cluster.worker

Fixes: #1304
PR-URL: #1386
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>

Copy link
Copy Markdown
Contributor

Thanks, landed in 5883a59.

brendanashworth removed their assignment May 9, 2015
Fishrock123 added a commit to Fishrock123/node that referenced this pull request May 15, 2015
PR-URL: nodejs#1679

Notable Changes:

* win,node-gyp: the delay-load hook for windows addons has now been
correctly enabled by default, it had wrongly defaulted to off in the
release version of 2.0.0 (Bert Belder) nodejs#1433
* os: tmpdir()'s trailing slash stripping has been refined to fix an
issue when the temp directory is at '/'. Also considers which slash is
used by the operating system. (cjihrig) nodejs#1673
* tls: default ciphers have been updated to use gcm and aes128 (Mike
MacCana) nodejs#1660
* build: v8 snapshots have been re-enabled by default as suggested by
the v8 team, since prior security issues have been resolved. This
should give some perf improvements to both startup and vm context
creation. (Trevor Norris) nodejs#1663
* src: fixed preload modules not working when other flags were used
before --require (Yosuke Furukawa) nodejs#1694
* dgram: fixed send()'s callback not being asynchronous (Yosuke
Furukawa) nodejs#1313
* readline: emitKeys now keeps buffering data until it has enough to
parse. This fixes an issue with parsing split escapes. (Alex Kocharin)
* cluster: works now properly emit 'disconnect' to cluser.worker (Oleg
Elifantiev) nodejs#1386
events: uncaught errors now provide some context (Evan Lucas) nodejs#1654
Fishrock123 pushed a commit to Fishrock123/node that referenced this pull request May 19, 2015
Inside of a worker, disconnect event was not emitted on cluster.worker

Fixes: nodejs#1304
PR-URL: nodejs#1386
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
This file contains hidden or 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cluster Issues and PRs related to the cluster subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants


Back | FazBrowse Home | New Git URL