Skip to content

Conversation

@lance
Copy link
Member

@lance lance commented Oct 2, 2017

Removing the REPL's lineParser.shouldFail checks resolves the issue below and does not cause any regressions in the test suite. It appears that when editorMode was backported to the 6.x branch, the LineParser failure checks were not removed.

Fixes: #15704
Ref: 39d9afe
Ref: 4875aa2

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
Affected core subsystem(s)

repl

@nodejs-github-bot nodejs-github-bot added repl Issues and PRs related to the REPL subsystem. v6.x labels Oct 2, 2017
@Fishrock123
Copy link
Contributor

@lance Is this a backport? What was the original commit / PR?

cc @MylesBorins

@lance
Copy link
Member Author

lance commented Oct 2, 2017

@Fishrock123 hmm - well, it's a partial backport of 39d9afe but incomplete. I think I need to mark this as a WIP for now.

@lance lance changed the title repl: don't use lineParser for Recoverable errors [WIP] repl: don't use lineParser for Recoverable errors Oct 2, 2017
Move the core logic from `LineParser` should fail handling into the
recoverable error check for the REPL default eval.

Fixes: #15704

PR-URL: #6171
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
@lance
Copy link
Member Author

lance commented Oct 4, 2017

Closing this PR to do a real backport PR as outlined in the backporting-to-release-lines.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

repl Issues and PRs related to the REPL subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants