Skip to content

NodeAgent: Execute scripts in dedicated VM#28

Merged
rwaldron merged 1 commit intotc39:masterfrom
bocoup:defensive-node
Jul 27, 2017
Merged

NodeAgent: Execute scripts in dedicated VM#28
rwaldron merged 1 commit intotc39:masterfrom
bocoup:defensive-node

Conversation

@jugglinmike
Copy link
Copy Markdown
Contributor

No description provided.

@jugglinmike jugglinmike requested a review from bterlson July 26, 2017 20:19
@jugglinmike
Copy link
Copy Markdown
Contributor Author

@bterlson I've added a test for cross-realm interactions as per your request in IRC. Note that it does not assert error names. This vagueness is intentional because not all hosts currently report the correct error, but that's a detail for Test262 to validate.

Comment thread test/runify.js Outdated
`).then(function(result) {
assert.equal(result.stderr, '');
assert(result.stdout.match(/^okay\r?\n/m));
});;
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.

nit: extra ; and strange indent

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Got it

Comment thread test/runify.js Outdated
print($.evalScript('let eshost;').type);
print($.evalScript('let eshost;').type);
`)
.then(function(result) {
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.

nit: all other tests are using arrow function syntax. This is not a blocker in any practical sense, but consistency is ideal.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The file is largely inconsistent in this regard, but I'm happy to use arrows here if you prefer.

@jugglinmike
Copy link
Copy Markdown
Contributor Author

Thanks for the review, @rwaldron. It should be all set

@bterlson
Copy link
Copy Markdown
Member

whoops, I conflicted this one with #30. @jugglinmike can you rebase?

@jugglinmike
Copy link
Copy Markdown
Contributor Author

@bterlson Sure. Rebased on master, resolving conflicts and fixing up fixup commits.

(For posterity, the original version of this branch is available here).

@rwaldron
Copy link
Copy Markdown
Contributor

With the conflicts resolved, I will assume @bterlson is 👍

@rwaldron rwaldron merged commit 492b29e into tc39:master Jul 27, 2017
@jugglinmike
Copy link
Copy Markdown
Contributor Author

Thank you both!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants