-
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
[v8.x backport] repl: remove internal frames from runtime errors #16457
Conversation
I left Local build failure stack traces
Edit: This has been resolved |
CI: https://ci.nodejs.org/job/node-test-pull-request/10971/ Edit: several failures - all of which seem to be unrelated. |
b183192
to
fc8acc8
Compare
lib/repl.js
Outdated
self.parseREPLKeyword = util.deprecate( | ||
_parseREPLKeyword, | ||
'REPLServer.parseREPLKeyword() is deprecated', | ||
'DEP0075'); |
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.
97c2301
to
ab0d7a6
Compare
@gibfahn good catch! Fixed (I think). I had to add New CI: https://ci.nodejs.org/job/node-test-pull-request/11118/ |
lib/repl.js
Outdated
* @param {keyword} keyword The command entered to check. | ||
* @return {Boolean} If true it means don't continue parsing the command. | ||
*/ | ||
REPLServer.prototype.parseREPLKeyword = function(keyword, rest) { |
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.
Isn't this function already defined here?
Lines 1053 to 1066 in edb03cb
/** | |
* Used to parse and execute the Node REPL commands. | |
* | |
* @param {keyword} keyword The command entered to check. | |
* @return {Boolean} If true it means don't continue parsing the command. | |
*/ | |
REPLServer.prototype.parseREPLKeyword = function(keyword, rest) { | |
var cmd = this.commands[keyword]; | |
if (cmd) { | |
cmd.action.call(this, rest); | |
return true; | |
} | |
return false; | |
}; |
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.
Hmm - that's disconcerting enough for me to want to start over on this. I'll take a look..
Update: bad cherry picking on my part. I will fix and push. My apologies.
Don't think function should be declared twice.
When a user executes code in the REPLServer which generates an exception, there is no need to display the REPLServer internal stack frames. PR-URL: #15351 Reviewed-By: Prince John Wesley <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Refs: #9601
Another CI after latest push https://ci.nodejs.org/job/node-test-pull-request/11499/ |
468562c
to
b05ef97
Compare
2233a64
to
053eba0
Compare
563f1f6
to
6fa51d6
Compare
When a user executes code in the REPLServer which generates an exception, there is no need to display the REPLServer internal stack frames. PR-URL: #15351 Backport-PR-URL: #16457 Reviewed-By: Prince John Wesley <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Refs: #9601
CI failures were from the v8.x-staging branch AFAICT. Landed in 6deae6e Thanks @lance ! |
When a user executes code in the REPLServer which generates an
exception, there is no need to display the REPLServer internal
stack frames.
PR-URL: #15351
Reviewed-By: Prince John Wesley [email protected]
Reviewed-By: James M Snell [email protected]
Reviewed-By: Ruben Bridgewater [email protected]
Refs: #9601
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
repl