-
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
inspector: code cleanup #21070
inspector: code cleanup #21070
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but this really should have been multiple commits for easier review and bisecting.
@refack What verification do you mean? Is there something I need to setup? |
You can disregard that last comment from refack... It was caused by a misconfigured Jenkins bot |
Thanks for the reviews. I uploaded a new revision of the test case, cannot figure out why it does not compile on Windows. Note that this PR is PR 1 of 3 (planned currently) that is laying the groundwork for the workers support. |
Windows issue should be resolved now (it was a test problem). |
There seems to be intermittance in one test on Windows. I tried a stress test (100 runs): https://ci.nodejs.org/job/node-stress-single-test/1907/nodes=win2012r2-mp-vs2017/console - it said that 100 runs out of 100 were ok (for some reason it still said the test was flaky, I suppose it is test harness bug). I do not know if that is flakiness and if it is, whether this change introduced it. I would like to proceed landing this change to unblock next changes that build on top of this one. |
Remove some unused code from the WS server implementation and switch to smart pointers where possible. PR-URL: #21070 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Pre-merge CI - https://ci.nodejs.org/job/node-test-pull-request/15262/ Fails on Windows bot on test-async-hooks, seems to be unlikely to be caused by this PR. |
Remove some unused code from the WS server implementation and switch to smart pointers where possible. PR-URL: #21070 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Remove some unused code from the WS server implementation and switch to
smart pointers where possible.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes