From tcsetpgrp(3):

If tcsetpgrp() is called by a member of a background process group in its session, and the calling process is not blocking or ignoring SIGTTOU, a SIGTTOU signal is sent to all members of this background process group.

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

1.11.2

Expected result

When autosave/netsave.sav would be overwritten, the savegame instead gets written to autosave/netsave2.sav, then autosave/netsave3.sav, and so on and so forth. At a certain point, the numbering wraps around back to 1 in order to prevent the autosave/netsave#.sav from taking up too much storage space.

Actual result

When `autosave/n

@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

this will help users to see if they are using integrated graphics or not.

Can be queried from the VisualServer:
https://docs.godotengine.org/fi/stable/classes/class_visualserver.html#class-visualserver-method-get-video-adapter-name

Also would be nice to show the current used video memory and used renderer

https://docs.godotengine.org/fi/stable/classes/class_visualserver.html#class-visual

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