Joel Dice

Running all the integration tests in parallel did eventually fail, but this time it was a different error on test: ``` failures: ---- integration_tests::test_wasi_http_hash_all stdout ---- Error: error sending request...

I think https://github.com/fermyon/spin/pull/2019 will help us diagnose these better.

We might need to punt and retry any tests that use the network up to N times if there's no obvious culprit here. It might also help to force them...

One other thought: I know that both Linux and MacOS have kernel-level heuristics for detecting and mitigating TCP SYN flood attacks, which I've had to explicitly disable when running load...

I approve this license change

Oops, the new step shouldn't be run on macOS, obviously. I'll fix that.

Yeah, that all sounds great to me, and I 100% agree that there's a lot of duplicated and wasted effort, including the redundant builds of the sysroot and the `ubuntu-latest`...

I just pushed an update; now we _only_ build for Linux/ARM64 as part of the `dockerbuild` job since `dist-ubuntu-bionic` is the build we actually care about.

> Idea: it might worth to propose WASI-Websockets to the CG meeting to formally define the WIT worlds and interfaces for websockets. Another possibility would be to reuse `wasi-messaging` and...

Current thinking is we'll build this into Spin rather than make it a plugin: https://github.com/fermyon/spin/pull/2212