Currently register looks like:

   private static <T> void register(Map<T, T> substitutions, T annotated, T original, T target) {
        if (annotated != null) {
            guarantee(!substitutions.containsKey(annotated) || substitutions.get(annotated) == original || substitutions.get(annotated) == target, "Already registered: %s", annotated);
            substitutions.put(annotated,

Version

Chakra-1.11.24

Execution step

./ChakraCore/out/Release/ch testcase.js

Testcase

target = Function();
handler = {
    get: function() {
        print('Run here');
    }
};
var p= new Proxy(target, handler);
new p;

Output

Expected behavior

Run here

Description

When ex

Task

Convert CI to GitHub Actions

Context

Travis is removing its free tier for OSS projects, so this should be built with GitHub Actions instead, which is not going to add additional cost.

I would expect this to be one of the easier projects to convert given that Docker isn't used in the build.

See also:

https://github.com/mvdan/github-actions-golang
https://github.com/ac

Using the following YAML should output warnings per offending spec instead of ignoring them silently.
Example:

footloose create
WARN[0000] Options under "spec.ignite" for "manager-%d" are ignored when using the "docker" backend
WARN[0000] Options under "spec.ignite" for "worker-%d" are ignored when using the "docker" backend
INFO[0000] Docker Image: quay.io/footloose/ubuntu18.04 prese

To Reproduce
Steps to reproduce the behavior:

1. Run make all as described in README.md and follow install process.
2. After install, macOS-VM.efi.vdi and macOS-VM.vdi are located directly in ~/VirtualBox VMs instead of ~/VirtualBox VMs/macOS-VM as is typical for VirtualBox VMs.

Expected behavior
After install, macOS-VM.efi.vdi and macOS-VM.vdi should be located in `~/

The check block in the peer-communication.ts example should be updated to the latest fork.

The following PR can be used for guidance ethereumjs/ethereumjs-devp2p#54 (this is missing the header RLP though).

Hi!
First, thanks for the guide, I enjoyed it 😃 I am wondering if there are test-images or something that extensively test if things are implemented correctly? The code I came up with does not match your example code exactly and I'd like to see if would make a difference in a hypothetical "compliance test suite".

It would be great to add the Quake 3 JIT compiler (e.g. for x86 or ARM).