-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
debugger: remove obsolete setTimeout #7154
Conversation
LGTM if CI is green |
Alas, it fails on Windows. https://ci.nodejs.org/job/node-test-binary-windows/2425/
|
@Trott what happens if you use |
CI with change to |
|
Re-running CI again because all the ARM stuff blew up, wow: https://ci.nodejs.org/job/node-test-pull-request/2925/ |
LGTM. The CI blew up again though. |
self.resume(); | ||
}); | ||
}, 10); | ||
setImmediate(() => { self.run(function() { self.resume(); }); }); |
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.
self.run(self.resume)
?
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.
Also can you drop self
for this
now?
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.
Also can you drop self for this now?
Oh, right, arrow functions, lexical binding...
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.
self.run(self.resume)
?
test/parallel/test-debugger-util-regression.js
fails if self.resume
/this.resume
is not wrapped in a function. (I did not look to see why...)
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.
Probably because of this
not being set properly.
Post-nit-fix CI: https://ci.nodejs.org/job/node-test-pull-request/2932/ |
self.resume(); | ||
}); | ||
}, 10); | ||
setImmediate(() => { this.run(() => { this.resume; }); }); |
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.
You're no longer calling resume()
?
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.
Heh, looks like we don't have a test that covers that. Guess I'll be adding one.
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.
It seems that .resume()
might be unnecessary:
Still LGTM |
Remove obsolete `setTimeout()` introduced in 3148f14. The fix for the problem is in b266074. (For the record, I mostly don't know what I'm talking about here but am summarizing from an IRC #node-dev conversation with @indutny on 04-Jun-2016.) PR-URL: nodejs#7154 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Landed in 671cffa |
Remove obsolete `setTimeout()` introduced in 3148f14. The fix for the problem is in b266074. (For the record, I mostly don't know what I'm talking about here but am summarizing from an IRC #node-dev conversation with @indutny on 04-Jun-2016.) PR-URL: #7154 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@Trott lts? |
@thealphanerd I think so, but maybe check with @indutny ? |
If CI is good - LGTM |
Remove obsolete `setTimeout()` introduced in 3148f14. The fix for the problem is in b266074. (For the record, I mostly don't know what I'm talking about here but am summarizing from an IRC #node-dev conversation with @indutny on 04-Jun-2016.) PR-URL: #7154 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Remove obsolete `setTimeout()` introduced in 3148f14. The fix for the problem is in b266074. (For the record, I mostly don't know what I'm talking about here but am summarizing from an IRC #node-dev conversation with @indutny on 04-Jun-2016.) PR-URL: #7154 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Remove obsolete `setTimeout()` introduced in 3148f14. The fix for the problem is in b266074. (For the record, I mostly don't know what I'm talking about here but am summarizing from an IRC #node-dev conversation with @indutny on 04-Jun-2016.) PR-URL: #7154 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Remove obsolete `setTimeout()` introduced in 3148f14. The fix for the problem is in b266074. (For the record, I mostly don't know what I'm talking about here but am summarizing from an IRC #node-dev conversation with @indutny on 04-Jun-2016.) PR-URL: #7154 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Remove obsolete `setTimeout()` introduced in 3148f14. The fix for the problem is in b266074. (For the record, I mostly don't know what I'm talking about here but am summarizing from an IRC #node-dev conversation with @indutny on 04-Jun-2016.) PR-URL: #7154 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Checklist
Affected core subsystem(s)
debugger
Description of change
Remove obsolete
setTimeout()
introduced in 3148f14. The fix for theproblem is in b266074. (For the record, I mostly don't know what I'm
talking about here but am summarizing from an IRC #node-dev conversation
with @indutny on 04-Jun-2016.)
R=@indutny