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.

The purpose of this work is to improve debug-ability.
J9JITConfig is a data structure used by both the VM and the JIT. It is attached to J9JavaVM and thus readily available from many custom OpenJ9 debugging tools.
TR::CompilationInfo is a data structure that holds a lot of information about other data structures in the JIT. The JIT creates a single such object and stores its address into t

Depends on #1048

Another Ethers issue 😄 : I lately had the use case where I wanted to pull in some tx data via RPC with Ethers which I wanted to use in some client testing context but I finally gave up since the conversion to our tx format here was not so clearly spottable and I used some direct client data extraction

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.