-
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
deleting property in vm context has no effect #6287
Labels
vm
Issues and PRs related to the vm subsystem.
Comments
Related to #6283 |
AnnaMag
added a commit
to AnnaMag/node
that referenced
this issue
Dec 14, 2016
Deleting property in the vm context has no effect nodejs#6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes.
3 tasks
AnnaMag
added a commit
to AnnaMag/node
that referenced
this issue
Dec 14, 2016
Deleting property in the vm context has no effect as reported in nodejs#6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes.
3 tasks
AnnaMag
added a commit
to AnnaMag/node
that referenced
this issue
Dec 16, 2016
Deleting property in the vm context has no effect as reported in nodejs#6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes.
cjihrig
pushed a commit
to cjihrig/node
that referenced
this issue
Dec 20, 2016
Deleting property in the vm context has no effect as reported in nodejs#6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes. PR-URL: nodejs#10272 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Merged
Merged
3 tasks
fhinkel
added a commit
to fhinkel/node
that referenced
this issue
Feb 10, 2017
In the implementation of the vm module, if a property is successfully deleted on the sandbox, we also need to delete it on the global_proxy object. Therefore, we must not call args.GetReturnValue().Set(). We only intercept, i.e., call args.GetReturnValue().Set(), in the DeleterCallback, if Delete() failed, e.g. because the property was read only. Fixes nodejs#6287
Fixed in #11266 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Example failure:
Expected
sbox.x
to beundefined
.The text was updated successfully, but these errors were encountered: