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

Right now, if the bootstrap process fails part of the way through, it leaves a bunch of invalid resources around in the cluster (like the old CSR). As a new user, it would be helpful if I didn't have to clean these up manually after a bootstrap fail.

Requirements:

• Clean up auth certificate CSR on failure

Questions:

• ~Should we clean up anything else? Cleaning up local config sounds da

For future reference:
https://github.com/yonaskolb/XcodeGen
https://github.com/tuist/tuist/

We just see that people forget adding new demo files to the demo Xcode project, and this can and should be automated after all.

This issue is for tracking the overall progress of upstreaming our changes, please post here if you create any new PRs with our changes in the upstream repository:

• [stdlib] fix return type of getNumRuntimeFunctionCounters apple/swift#24182. Status: merged.
• [stdlib] Fix return type of swift_{uint64,int64,float*}ToString h

https://github.com/mathetake/gasm/blob/52edbd17a5a15da3f201baffe011f9f562167606/wasm/vm_num_test.go#L3

On blur, we should call this.xterm.scrollToBottom(). 😄

For wasi-worker-cli add option --yew so that
wasiworker init --yew should create yew worker template

Yew worker template should be based on wasi-worker-yew crate as per example