Jimmy Thomson

AcmeAir benchmark seems very noisy

6

I've been trying to benchmark Node-ChakraCore using the AcmeAir benchmark, and I'm getting a lot of noise in the throughput results. Is there any guidance on how to set up...

SharedArrayBuffers can cause crashes when inspected in certain ways

3

Something non-obvious has changed between the current state of things and the nightly integration I'm about to complete, which causes shared array buffers to return a null pointer for their...

Need to add support for es modules

14

Node 8.5.0 is adding support for es modules, but the approach they are taking using v8 APIs does not fit well with ChakraCore's approach to modules. In particular, ChakraCore combines...

vm.runInContext is not fully supported after upstream change

17

With the inclusion of https://github.com/nodejs/node/pull/16293 we need to make some additional changes to properly support `vm.runInContext`. When running `vm.runInContext(code, context)` the context object is intended to act like the global...

N-API modules building against node-chakracore must use custom npm

1

We have made a small change to npm in this repo, part of eeec9f1bae074bceccb80e423abfd8a811e08f51 Without that change, attempting to build a N-API module (or probably any native module?) against node-chakracore...

* **Version**: master * **Platform**: all * **Subsystem**: inspector `tests/inspector/test-context.js` is failing because the test expects to be able to create and destroy contexts, and have relevant events fired by...

test-break-when-eval fails to evaluate expression

1

* **Version**: master * **Platform**: all * **Subsystem**: inspector The `test-break-when-eval` test is failing with a timeout because the test attempts to evaluate an expression while the JS engine is...

* **Version**: v8.0.0-nightly20170417265fc0bedc * **Platform**: Windows 64-bit * **Subsystem**: REPL When using the node REPL interactively, typing some invalid (to my knowledge) symbols will cause node-v8 to prompt for further...

HTTP2 functionality requires changes to work with TTD

16

* **Version**: master * **Platform**: all * **Subsystem**: TTD, http2 Some changes to http2 require updates to support TTD properly: the upstream commit is https://github.com/nodejs/node/commit/e46ae99a2a8153d6af84dbf2883f5f0938065a3e and will need similar changes...

The @web/test-runner-core package includes the `TestRunnerCli` class, which always has a `DynamicTerminal` that it references that has no knowledge of the `staticLogging` configuration variable. The `TestRunnerCli` will do things like...