Lann

It turns out the only field that really matters here is `allowed_http_hosts` / `allowedHttpHosts`. Fixing this will require updating hippo, which does expect `allowedHttpHosts`: https://github.com/deislabs/hippo/blob/c9c09e9df6b38787e7817754ce6660bad566dc57/src/Infrastructure/Services/BindleService.cs#L63 https://github.com/deislabs/hippo/blob/627b51e1ef368349c964353e7dab591157ce9278/src/Application/Common/Interfaces/BindleService/RevisionComponent.cs#L23

Removing `-no-debug` from the `tinygo` build command and running spin with `WASMTIME_BACKTRACE_DETAILS=1` gives more detail: ``` 2: 0x141d9 - realloc at /usr/lib/tinygo/src/runtime/arch_tinygowasm.go:136:28 ```

Finally getting back to this... The backtrace appears to point at the indexing operation here: ```go ptr := unsafe.Pointer(&buf[0]) ``` Suggesting that the panic could be caused by `buf` having...

This makes sense with the patch identified in https://github.com/fermyon/spin/issues/820#issuecomment-1280726355, which changed the underlying `realloc` implementation. I'm testing a patch to tinygo.

Bonus points if this could be dynamic, e.g. `http://mybart.dev/blog-post-1?content_url=https://raw.githubusercontent.com/fermyon/bartholomew/main/docs/content`, though this would need careful consideration from a security perspective as it would be a potential XSS vector.

Perhaps a race between the execution of `jobs -p` and `kill` (delayed waiting on sudo prompt)? I wonder if the original issue is some oddness around cgroups on The Linux...

@FrankYang0529

@FrankYang0529 as the original author of the GCP work, any concerns here?

Red flavored diffs are the best diffs

Maybe. I think the main point is that it's odd for the version to include 0.4 _after_ 0.4 is released. It may be that we actually need to update our...