wasi

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

this is fairly minor, but kind of annoying when you need to inject the CA content into the file, and they might technically be coming from different sources

https://github.com/deislabs/krustlet/blob/9efb832edb288ba86822bd62e80e3f9f5e68e37b/crates/kubelet/src/bootstrapping/mod.rs#L70

It'd be nice if this could try to check for either field (certificate_authority or certificate_authority_data)

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

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