virtual-machine

When passing Wasm function to the host as a callback, it's passed as an index in the table.
Wasm3 needs to provide an API to call such functions.

If I execute an alias on an instance and that instance is not running, I would expect the instance to be automatically started and then the alias executes. A message should be printed out saying what is happening.

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

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

Adding the new debugging capabilities (see title) within the devp2p packages along #1449 had the side effect of producing redundant messages on certain DEBUG logger combinations, mostly visible if the plain devp2p:* logger is used, see e.g.:

This is distracting and reduces ove

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