Lann

> It's intentional that build shouldn't break over a bad kebab etc To clarify: you're saying that you want build to work when the manifest is otherwise invalid? Is that...

> I think we now expose something closer to a 'raw schema' stage, so maybe that's an acceptable compromise. Yeah that was part of my intention with the Great `spin-manifest`...

:point_up: This hopefully fixed it.

Certainly _possible_ but self-update mechanisms are quite tricky to get right, especially cross-platform.

Hi @k0pernicus, thanks for the report. We are currently planning to drop support for Swift with Spin 3.0 because of [limitations in the Swift toolchain](https://github.com/fermyon/spin/issues/2774#issuecomment-2315774364) that the 2.7 template is...

I'd be interested to see how different preopen patterns interact with wasi-libc. For instance, if I have a preopen with guest path `x/y`, does that appear as `/x/y` to libc?

> Hi @lann, could you please point me to how could I verify that with wasi-libc specifically? Most wasi implementations are using wasi-libc (via wasi-sdk), so just experimenting with e.g....

For interop with existing code I think its best for wasi's filesystem to always have a "conventional" full tree structure; I know I have personally written plenty of code that...

> But as @seungjin already mentioned: What are the implications of running with --disable-pooling? Under some circumstances you would expect reduced performance under high load. That is probably not a...

> I wonder if these systems also restrict the amount of virtual memory available? I think this is likely, via either the `vm.overcommit_memory` kernel param or maybe `ulimit -v`.