Since state is a reserved keyword in Truffle's guard mechanism, it should not be possible to use it in a guard definition as this can cause serious problems. The annotation processor should either reject the state keyword in guard definitions or the state temporary variable produced by the processor should be renamed to avoid this conflict.

Here's an example:
<img width="629" alt="screen

Hello,
I run following code in ch 1.11.19(debug)，and it will crash by an assertion.

let b = [1.1, 2.2, 3.3];
b[4294967294] = 3;
Array.prototype.copyWithin.call(b, 0, 1);

Crash output:

ASSERTION 7690: (/.../ChakraCore-1.11.19/lib/Runtime/Library/JavascriptArray.cpp, line 9309) direction == -1 || (fromVal + count < MaxArrayLength && toVal + count < MaxArrayLength)
 Failure: (d

I reinstalled a k3s cluster built with --no-extras and added `--k3s-extra-args="--flannel-backend=host-gw". The cluster failed to start.

I logged in and saw that the output of ps showed the following:

14760 ?        Ssl    0:40 /usr/local/bin/k3s server --cluster-init --tls-san 10.68.0.63 --flannel-backend=host-gw--n

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 `~/

I'm trying to use ethereumjs-blockchain to read the raw levedb data created by geth, but I failed to do so.
And I also try to use the dbManager to read the levedb data, failed again. My steps are:

1. sync some the blockchain data by using geth --goerli --datadir <my data dir>
2. write code to read the level db data.

const level = require('level');
const DbManager = requ

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

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".