-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Repl eval() with context ignored in 10.2.0+ #20965
Labels
Comments
addaleax
added
repl
Issues and PRs related to the REPL subsystem.
regression
Issues related to regressions.
labels
May 25, 2018
I’d just revert the patch for now. Thoughts? |
IMO since the bit reverted would be just extra hints a revert would be ok. |
cjihrig
added a commit
to cjihrig/node
that referenced
this issue
May 28, 2018
This reverts commit 9aa4ec4. This commit in question introduced a regression in repl.eval(), as the context argument is no longer passed to runInContext(). PR-URL: nodejs#20972 Fixes: nodejs#20965 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: John-David Dalton <john.david.dalton@gmail.com>
Thank you @cjihrig! |
MylesBorins
pushed a commit
that referenced
this issue
May 29, 2018
This reverts commit 9aa4ec4. This commit in question introduced a regression in repl.eval(), as the context argument is no longer passed to runInContext(). PR-URL: #20972 Fixes: #20965 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: John-David Dalton <john.david.dalton@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The commit here 9aa4ec4 has caused default
repl#eval
to ignore thecontext
parameter passed to it. The issue was introduced in PR #20617 (issue #19021).The text was updated successfully, but these errors were encountered: