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

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

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.

Motivation

Working with our game logs, for instance when investigating a crash or other kind of issue, is annoying because there's a lot of (unnecessary) noise in them, that we learn to accept / ignore instead of reducing it.
One part of the log noise is complaints regarding unknown components or component fields.

Proposal

1. Investigate the common complaints regarding unknown co

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

Tell us how you think we can improve Sandpack

Improve the test coverage in the read-only mode feature and in the editorState state.

Possible cases

editorState

• Render a Sandpack from scratch and make sure the editorState has the initial value (pristine);
• Render a Sandpack, update any file content, and make sure the editorState is set to dirty;
• Render a Sandpack

could make the chemoreceptor auto select the compound's colour when selecting one, this would make it faster to configure multiple chemoreceptors for different compounds to look for.

Just needs a callback for the option button to detect when it changes value, and then just looking up the compound colour and setting that on the colour picker. Could maybe only change the colour if it is white or

nanovms/ops#525

https://github.com/DMOJ/judge-server/blob/efc9f427e003f97c258a8aa82b6ce2d6de643ca5/dmoj/problem.py#L275

This would allow site-managed generators to be written in more than C++. We already store known extensions in the Executor classes.