sandbox

Now that we have the checklocks analyzer, we should annotate values that are lock-protected with an appropriate checklocks attribute.

In bytecodealliance/wasmtime#2497 (comment) we added support for generating nested modules, and we generate these modules by concatenating strings of WAT and then passing it to Module::new which internally checks for WAT strings and assembles them into Wasm bytes if necessary.

We can make this more efficient, improving the number of test cases we fuzz in a

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.

Version of OpenTTD

Since e04ca904a9455afc63aa87db775fe4463ab899b7

The introduction of the minimap screenshot feature appears to be duplicating functionality that will be used elsewhere for drawing the widgets within the minimap window; specifically, the GetMinimapOwner function is very likely to be replicating functionality used by the owner information overlay of the minimap window.

I just saw in auto-evo a place where energy balance is computed twice just a few rows apart:
https://github.com/Revolutionary-Games/Thrive/blob/28e604b61f63162dd44f54bd450fcbd8cd93674b/src/auto-evo/simulation/PopulationSimulation.cs#L191

this should be super simple to just store that in a variable instead of computing it twice, should give at least a tiny performance benefit.

The virtio_scsi driver enqueues buffers to the eventq but does not actually handle them on completion. The following events could be reported to the driver which require some action to be taken:

• transport reset: This may occur as a result of hotplug events or a device being reset. Sense codes cannot be relied on when new devices or busses appear, so this event needs to be handled.
• asynchro

nanovms/ops#525

It wasn't present in Python 2, hence why we have NullStdoutMixin. Nowadays, we could do it directly in tracer.py, and drop NullStdoutMixin.

Code located in drakrun is quite fragile and complex, often interacting with rest of the system since it:

• sets up network interfaces
• changes iptables rules
• spawns/destroys VMs
• etc.

The most critical code paths are installation and task consumer loop.
Ideally, we should have 100% code coverage however I don't expect that it's going to happen instantly.
Simple, pure functions ca