sandbox

The doc says

	// Unlike io.Writer.Write, Endpoint.Write transfers ownership of any bytes
	// successfully written to the Endpoint. That is, if a call to
	// Write(SlicePayload{data}) returns (n, err), it may retain data[:n], and
	// the caller should not use data[:n] after Write returns.

but the signature of Write has since changed. It no longer accepts a slice payload, so this

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

12.0-beta2

Expected result

See somewhere on the vehicle or wherever, that the ship is lost.

Actual result

If a ship cannot reach its destination, it shows news about that once. This is true for all vehicles, but for ships even more annoying as they tend to drift towards the destination.

If you think you fixed the route, it doesn't update you with "route found

@keturn proposed the following changes as a follow-up for the migration of our pipeline Jenkinsfile from scripted to declarative syntax in #4784:

• Move discoverGitReferenceBuild as early as possible.
• Publish stage: Refactor "rebuild Omega after engine trunk build" to not need script block
• Analytics and Documenta

in order to not overlap with the new patch name location text

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

Regressed in DMOJ/judge-server#673, since now the cache is per-worker-process, and gets destroyed on exit. Will require a rewrite of the caching system.

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