Skip to content

Partial fix for #864 - report property attributes from sandbox object - #885

Closed
smikes wants to merge 1 commit into
nodejs:v1.xfrom
smikes:gh-864-failing-test
Closed

Partial fix for #864 - report property attributes from sandbox object#885
smikes wants to merge 1 commit into
nodejs:v1.xfrom
smikes:gh-864-failing-test

Conversation

@smikes

Copy link
Copy Markdown
Contributor

Here's a failing test for issue #864

@cjihrig

Copy link
Copy Markdown
Contributor

Please do not merge this in while the test is still failing.

GlobalPropertyQueryCallback() was returning `None`
as attributes for all properties, without regard
to actual properties settings.
This patch looks up attributes for sandbox-defined
properties and returns them. Partial fix for nodejsgh-864
Add test for nodejsgh-864, non-default settings of
object properties (e.g., `enumerable: false`) are not
visible when object is used as a sandbox
@smikessmikes changed the title add failing testPartial fix for #864 - report property attributes from sandbox objectFeb 19, 2015
@smikes

Copy link
Copy Markdown
ContributorAuthor

Test is no longer failing; a change to node_contextify.cc is a partial fix for #864 and fixes the behavior tested in test-vm-preserves-property.js.

@smikes

Copy link
Copy Markdown
ContributorAuthor

Although this PR was originally inspired by #864, it is complete in itself and reports sandbox property attributes correctly.

The full fix for #864 may involve changes to v8 APIs upstream (see @bnoordhuis comments in #884).

In the meantime, I believe this PR is now ready for review.

Comment threadsrc/node_contextify.cc Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we also add if (in_proxy_global) { attr = proxy_global->GetPropertyAttributes(property); } as the fallback?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried that. It caused infinite recursion on proxy_global. I think @bnoordhuis has a patch into v8 to add a new api to support this.

That's why this change is "partial fix"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. Also given that per #855 I want to at least attempt to rip out proxy global entirely that might end up being unnecessary.

Probably want to leave a TODO(smikes) in the source code though for later.

@domenic

Copy link
Copy Markdown
Contributor

LGTM if you add a TODO. (I am not an official LGTM-er though.)

@brendanashworth

Copy link
Copy Markdown
Contributor

Is there an update on this? see

@mscdexmscdex added the vm Issues and PRs related to the vm subsystem. label Mar 22, 2015
@smikes

Copy link
Copy Markdown
ContributorAuthor

I will try to finish this this weekend.

@bnoordhuis

Copy link
Copy Markdown
Member

Apropos that V8 patch, it landed in v8/v8@726eb05 and should probably be back-ported. That makes it a semver-minor thing because it's a new public API. It's also going to break building against a shared libv8 that doesn't carry the patch. :-/

@domenic

Copy link
Copy Markdown
Contributor

@smikes any chance of landing this on next, with the updates?

Comment threadsrc/node_contextify.cc Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not HasRealNamedProperty ?

@domenic

Copy link
Copy Markdown
Contributor

Actually I think I can take this over.

chrisdickinson pushed a commit that referenced this pull request Jun 3, 2015
The GlobalPropertyQueryCallback was changed in 2010 to return an
integer instead of a boolean:
https://groups.google.com/forum/#!topic/v8-users/OOjHJrix-cU
This integer communicates the property descriptors of the property,
instead of just its presence or absence. However, the original
contextify code was probably written before this change, and it was
not updated when porting to Node.js.
Credit to @smikes for the test and the original PR of #885.
Fixes: #864Fixes: #885
PR-URL: #1773
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@bnoordhuis

Copy link
Copy Markdown
Member

Closing, fixed by a45fbfc.

domenic added a commit that referenced this pull request Jun 17, 2015
The GlobalPropertyQueryCallback was changed in 2010 to return an
integer instead of a boolean:
https://groups.google.com/forum/#!topic/v8-users/OOjHJrix-cU
This integer communicates the property descriptors of the property,
instead of just its presence or absence. However, the original
contextify code was probably written before this change, and it was
not updated when porting to Node.js.
Credit to @smikes for the test and the original PR of #885.
Fixes: #864Fixes: #885
PR-URL: #1773
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
domenic added a commit that referenced this pull request Jul 22, 2015
The GlobalPropertyQueryCallback was changed in 2010 to return an
integer instead of a boolean:
https://groups.google.com/forum/#!topic/v8-users/OOjHJrix-cU
This integer communicates the property descriptors of the property,
instead of just its presence or absence. However, the original
contextify code was probably written before this change, and it was
not updated when porting to Node.js.
Credit to @smikes for the test and the original PR of #885.
Fixes: #864Fixes: #885
PR-URL: #1773
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
domenic added a commit that referenced this pull request Jul 24, 2015
The GlobalPropertyQueryCallback was changed in 2010 to return an
integer instead of a boolean:
https://groups.google.com/forum/#!topic/v8-users/OOjHJrix-cU
This integer communicates the property descriptors of the property,
instead of just its presence or absence. However, the original
contextify code was probably written before this change, and it was
not updated when porting to Node.js.
Credit to @smikes for the test and the original PR of #885.
Fixes: #864Fixes: #885
PR-URL: #1773
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
domenic added a commit that referenced this pull request Jul 30, 2015
The GlobalPropertyQueryCallback was changed in 2010 to return an
integer instead of a boolean:
https://groups.google.com/forum/#!topic/v8-users/OOjHJrix-cU
This integer communicates the property descriptors of the property,
instead of just its presence or absence. However, the original
contextify code was probably written before this change, and it was
not updated when porting to Node.js.
Credit to @smikes for the test and the original PR of #885.
Fixes: #864Fixes: #885
PR-URL: #1773
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
domenic added a commit that referenced this pull request Aug 1, 2015
The GlobalPropertyQueryCallback was changed in 2010 to return an
integer instead of a boolean:
https://groups.google.com/forum/#!topic/v8-users/OOjHJrix-cU
This integer communicates the property descriptors of the property,
instead of just its presence or absence. However, the original
contextify code was probably written before this change, and it was
not updated when porting to Node.js.
Credit to @smikes for the test and the original PR of #885.
Fixes: #864Fixes: #885
PR-URL: #1773
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
domenic added a commit that referenced this pull request Aug 3, 2015
The GlobalPropertyQueryCallback was changed in 2010 to return an
integer instead of a boolean:
https://groups.google.com/forum/#!topic/v8-users/OOjHJrix-cU
This integer communicates the property descriptors of the property,
instead of just its presence or absence. However, the original
contextify code was probably written before this change, and it was
not updated when porting to Node.js.
Credit to @smikes for the test and the original PR of #885.
Fixes: #864Fixes: #885
PR-URL: #1773
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
domenic added a commit that referenced this pull request Aug 4, 2015
The GlobalPropertyQueryCallback was changed in 2010 to return an
integer instead of a boolean:
https://groups.google.com/forum/#!topic/v8-users/OOjHJrix-cU
This integer communicates the property descriptors of the property,
instead of just its presence or absence. However, the original
contextify code was probably written before this change, and it was
not updated when porting to Node.js.
Credit to @smikes for the test and the original PR of #885.
Fixes: #864Fixes: #885
PR-URL: #1773
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
domenic added a commit that referenced this pull request Aug 4, 2015
The GlobalPropertyQueryCallback was changed in 2010 to return an
integer instead of a boolean:
https://groups.google.com/forum/#!topic/v8-users/OOjHJrix-cU
This integer communicates the property descriptors of the property,
instead of just its presence or absence. However, the original
contextify code was probably written before this change, and it was
not updated when porting to Node.js.
Credit to @smikes for the test and the original PR of #885.
Fixes: #864Fixes: #885
PR-URL: #1773
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

vmIssues and PRs related to the vm subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@smikes@cjihrig@domenic@brendanashworth@bnoordhuis@chrisdickinson@mscdex