GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||
GeezerVison is showing github.com — cluster: use ObjectPrototypeHasOwnProperty by daeyeon · Pull Request #48141 · nodejs/node Conversation
Member
This addresses: #48077 (comment) Signed-off-by: Daeyeon Jeong [email protected]
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Signed-off-by: Daeyeon Jeong <[email protected]>
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
|
There was an error while loading. Please reload this page.
|
On second thought as I added the test, I think that the builtin doesn't prevent changes to the process.env prototype. Closing as we don't have a clue it needs to be applied to cluster only. Thanks for the review! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
We can't avoid changes to process.env prototype, but we can avoid those prototype changes affecting the behavior of the cluster module and other modules. That's what this is about, right? I think we should re-open this. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Signed-off-by: Daeyeon Jeong <[email protected]>
|
Yes, that's right. This way is safer, but I thought there might be a reason why the properties of |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
It's possible that there would be significant negative performance implications in some hot paths, but I don't think this is one of those. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Landed in b4d5f1f |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Signed-off-by: Daeyeon Jeong <[email protected]> PR-URL: #48141 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Signed-off-by: Daeyeon Jeong <[email protected]> PR-URL: #48141 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Signed-off-by: Daeyeon Jeong <[email protected]> PR-URL: nodejs#48141 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Signed-off-by: Daeyeon Jeong <[email protected]> PR-URL: nodejs#48141 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Signed-off-by: Daeyeon Jeong <[email protected]> PR-URL: nodejs#48141 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.