virtual-machine

Related to metering wasm3/wasm3#127 and being able to run a set number of instructions, I'd like to be able to serialize a paused interpreter's state and deserialize it to a new interpreter instance; very roughly,

const interp = new wasm3.Interpreter(module);
interp.interpretNInstructions(100);
const interpState = interp.serializeState();
const interp2 = wasm3.In

What are you trying to do?
Currently all commands use instance name to perform operations. This makes operations on multiple instances difficult and requires individual commands/action on each instance. For example: if I have 3 VMs for apps, 2 vms for db, and I want to run a command on just db nodes, I would have to run two commands. Or If I have to reboot app servers, thats 3 commands.

Current, if we try to run a more recent Java class in an old JVM, we get the following error message:

Error: LinkageError occurred while loading main class some.Class
	java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=some/Class, offset=6

However, it is not so easily to detect that the class was compiled with a version above the supported by the JVM.Hotspot

There is actually a lot of redundancy between the ETH and LES protocol implementation. This should be combined into a superclass sitting between e.g. ETH and EventEmitter at some point. This will likely lead to a substantially cleaner implementation of the subclasses, increase readability as well as ease adding new features and avoid introducing consistency gaps along the way.

(this new sup

Field was moved in most recent API Version.
This looks hard to patch to make backwards compatible since the structs look to have been copied from ignite directly without use of kube api-machinery:
https://github.com/weaveworks/footloose/blob/8bd6cfc/pkg/ignite/inspect.go#L43

Some old programs versions can be found here if someone needs them to test old exploits for instance.